![]() | This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
|
Seems to a kind of smoke testing (or maybe a Microsoftism for the same concept). QVVERTYVS ( hm?) 01:32, 20 December 2013 (UTC)
See also previous discussion, which discussed merging into another article. QVVERTYVS ( hm?) 02:44, 20 December 2013 (UTC)
This article lacks one essential feature, the origin of the term. "Smoke testing" sounds idiomatic. -- Philip lamb ( talk) 02:59, 15 June 2018 (UTC)
Sanity testing#Software development suggests that "sanity testing", in software development, is the same as smoke testing, and it has a reference to corroborate this. QVVERTYVS ( hm?) 01:35, 20 December 2013 (UTC)
-- Qside ( talk) 14:56, 5 June 2014 (UTC)This article is talking about Intake Testing, which is distinct from smoketesting. Article should be renamed. Reference is...
Standard glossary of terms used in Software Testing V2.2 (dd. October 19th, 2012) Produced by the ‘Glossary Working Party’ International Software Testing Qualifications Board
http://science.df.lu.lv/kaab13/istqb_glossary_of_testing_terms_2.2.pdf
There can be a difference Smoke testing is Build Verification Test checks whether the build launches successfully after installation and Sanity testing is shallow testing done after regression is over with an intent to verify that end user requirements are met on not.(3rd paragraph of < /info/en/?search=Sanity_testing) [1]
I don't like idea of merging those 2 things.
Programmer can insert a sanity check in code in order to rule out if for example configuration of the program is sane.
Lets say a piece of code that checks if configuration entry describing the TCP port number is in fact a number and is below 65535.
In this meaning a sanity check is an inherent part of the program.
Smoke tests on the other hand are always something that comes from the outside.
Let it be a user testing if some basic functionalities are working or an automated test, that is not an inherent part of the running program.
Emergie ( talk) 17:44, 23 August 2016 (UTC)
References
The article should never have been created and I am being bold in redirecting until a decision has been made. The confusion has endured long enough. Walter Görlitz ( talk) 05:21, 20 December 2013 (UTC)
So why is it called a "smoke" test?
77.201.128.233 ( talk) 14:49, 28 February 2019 (UTC)
For me a smoke test, tests if the system works under heavy load.
I am not the only one who uses the term like this. Example:
https://smartbear.com/blog/test-and-monitor/7-types-of-web-performance-tests-and-how-they-fit/
Quote: 7. Smoke Test: A smoke test is a test run under very low load that merely shows that the application works as expected. The term originated in the electronics industry and refers to the application of power to an electronic component. If smoke is generated, the test fails and no further testing is necessary until the simplest test passes successfully. For example, there may be correlation issues with your scenario or script – if you can run a single user test successfully, the scenario is sound. It is a best practice to initate one of these “verification” runs before running larger tests to ensure that the test is valid. — Preceding unsigned comment added by Guettli ( talk • contribs) 10:34, 17 February 2020 (UTC)
![]() | This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
|
Seems to a kind of smoke testing (or maybe a Microsoftism for the same concept). QVVERTYVS ( hm?) 01:32, 20 December 2013 (UTC)
See also previous discussion, which discussed merging into another article. QVVERTYVS ( hm?) 02:44, 20 December 2013 (UTC)
This article lacks one essential feature, the origin of the term. "Smoke testing" sounds idiomatic. -- Philip lamb ( talk) 02:59, 15 June 2018 (UTC)
Sanity testing#Software development suggests that "sanity testing", in software development, is the same as smoke testing, and it has a reference to corroborate this. QVVERTYVS ( hm?) 01:35, 20 December 2013 (UTC)
-- Qside ( talk) 14:56, 5 June 2014 (UTC)This article is talking about Intake Testing, which is distinct from smoketesting. Article should be renamed. Reference is...
Standard glossary of terms used in Software Testing V2.2 (dd. October 19th, 2012) Produced by the ‘Glossary Working Party’ International Software Testing Qualifications Board
http://science.df.lu.lv/kaab13/istqb_glossary_of_testing_terms_2.2.pdf
There can be a difference Smoke testing is Build Verification Test checks whether the build launches successfully after installation and Sanity testing is shallow testing done after regression is over with an intent to verify that end user requirements are met on not.(3rd paragraph of < /info/en/?search=Sanity_testing) [1]
I don't like idea of merging those 2 things.
Programmer can insert a sanity check in code in order to rule out if for example configuration of the program is sane.
Lets say a piece of code that checks if configuration entry describing the TCP port number is in fact a number and is below 65535.
In this meaning a sanity check is an inherent part of the program.
Smoke tests on the other hand are always something that comes from the outside.
Let it be a user testing if some basic functionalities are working or an automated test, that is not an inherent part of the running program.
Emergie ( talk) 17:44, 23 August 2016 (UTC)
References
The article should never have been created and I am being bold in redirecting until a decision has been made. The confusion has endured long enough. Walter Görlitz ( talk) 05:21, 20 December 2013 (UTC)
So why is it called a "smoke" test?
77.201.128.233 ( talk) 14:49, 28 February 2019 (UTC)
For me a smoke test, tests if the system works under heavy load.
I am not the only one who uses the term like this. Example:
https://smartbear.com/blog/test-and-monitor/7-types-of-web-performance-tests-and-how-they-fit/
Quote: 7. Smoke Test: A smoke test is a test run under very low load that merely shows that the application works as expected. The term originated in the electronics industry and refers to the application of power to an electronic component. If smoke is generated, the test fails and no further testing is necessary until the simplest test passes successfully. For example, there may be correlation issues with your scenario or script – if you can run a single user test successfully, the scenario is sound. It is a best practice to initate one of these “verification” runs before running larger tests to ensure that the test is valid. — Preceding unsigned comment added by Guettli ( talk • contribs) 10:34, 17 February 2020 (UTC)