{"id":18349,"date":"2013-06-11T10:00:31","date_gmt":"2013-06-11T08:00:31","guid":{"rendered":"https:\/\/mamchenkov.net\/wordpress\/?p=18349"},"modified":"2013-06-11T10:00:31","modified_gmt":"2013-06-11T08:00:31","slug":"water-testing-is-not-a-term-for-software-testing","status":"publish","type":"post","link":"https:\/\/mamchenkov.net\/wordpress\/2013\/06\/11\/water-testing-is-not-a-term-for-software-testing\/","title":{"rendered":"Water testing is not a term (for software testing)"},"content":{"rendered":"<!-- google_ad_section_start -->\n<p>I&#8217;ve been hearing the term &#8220;water testing&#8221; for one of the work projects that I am involved in. \u00a0The term is used to describe the stage of the project when it&#8217;s available on the production servers with live data, but open only to a subset of the users. \u00a0After searching around for a bit, I can&#8217;t find a reference to this term anywhere, except the <a href=\"http:\/\/en.wikipedia.org\/wiki\/Water_testing\">water industry<\/a>:<\/p>\n<blockquote><p><b>Water testing<\/b>\u00a0is a broad description for various procedures used to analyze\u00a0water quality.<\/p><\/blockquote>\n<p>So that of course sent me on to the path of finding the correct term. \u00a0The closest by analogy that I heard of is &#8220;<a href=\"http:\/\/en.wikipedia.org\/wiki\/Smoke_testing\">smoke testing<\/a>&#8220;.<\/p>\n<blockquote><p>The plumbing industry started using the smoke test in 1875.<\/p>\n<p>Later this usage seems to have been forgotten, leading some to believe the term originated in the electronics industry: &#8220;The phrase\u00a0<i>smoke test<\/i>\u00a0comes from [electronic] hardware testing. You plug in a new board and turn on the power. If you see smoke coming from the board, turn off the power. You don&#8217;t have to do any more testing.&#8221;<\/p><\/blockquote>\n<p>Specifically for software development and testing:<\/p>\n<blockquote><p>In\u00a0computer programming\u00a0and\u00a0software testing,\u00a0<i>smoke testing<\/i>\u00a0is preliminary testing to reveal simple failures severe enough to reject a prospective software release. In this case, the smoke is metaphorical. A subset of test cases that cover the most important functionality of a component or system are selected and run, to ascertain if the most crucial functions of a program work correctly.\u00a0For example, a smoke test may ask basic questions like &#8220;Does the program run?&#8221;, &#8220;Does it open a window?&#8221;, or &#8220;Does clicking the main button do anything?&#8221; The purpose is to determine whether the application is so badly broken that further testing is unnecessary. As the book &#8220;Lessons Learned in Software Testing&#8221;\u00a0\u00a0puts it, &#8220;smoke tests broadly cover product features in a limited time &#8230; if key features don&#8217;t work or if key bugs haven&#8217;t yet been fixed, your team won&#8217;t waste further time installing or testing&#8221;.<\/p>\n<p>Smoke testing performed on a particular build is also known as a\u00a0<i>build verification test<\/i>.<\/p>\n<p>A daily build and smoke test is among industry best practices.<\/p><\/blockquote>\n<p>This sounds very much like &#8220;<a href=\"http:\/\/en.wikipedia.org\/wiki\/Sanity_testing\">sanity testing<\/a>&#8220;:<\/p>\n<blockquote><p>A\u00a0<b>sanity test<\/b>\u00a0or\u00a0<b>sanity check<\/b>\u00a0is a basic test to quickly evaluate whether a claim or the result of a calculation can possibly be true. It is a simple check to see if the produced material is rational (that the material&#8217;s creator was thinking rationally, applying\u00a0sanity). The point of a sanity test is to rule out certain classes of obviously false results, not to catch every possible error. A\u00a0rule-of-thumb\u00a0may be checked to perform the test. The advantage of a sanity test, over performing a complete or rigorous test, is speed.<\/p>\n<p>[&#8230;]<\/p>\n<p>In\u00a0computer science, a\u00a0<i>sanity test<\/i>\u00a0is a very brief run-through of the functionality of a\u00a0computer program, system, calculation, or other analysis, to assure that part of the system or methodology works roughly as expected. This is often prior to a more exhaustive round of testing.<\/p><\/blockquote>\n<p>After reviewing all sorts of <a href=\"http:\/\/en.wikipedia.org\/wiki\/Software_testing#Testing_Types\">testing types<\/a>, I think the correct term for our scenario is actually &#8220;<a href=\"http:\/\/en.wikipedia.org\/wiki\/Software_testing#Beta_testing\">beta testing<\/a>&#8220;:<\/p>\n<blockquote><p>Beta testing comes after alpha testing and can be considered a form of external\u00a0user acceptance testing. Versions of the software, known as\u00a0beta versions, are released to a limited audience outside of the programming team. The software is released to groups of people so that further testing can ensure the product has few faults or\u00a0bugs. Sometimes, beta versions are made available to the open public to increase the\u00a0feedback\u00a0field to a maximal number of future users.<\/p><\/blockquote>\n<!-- google_ad_section_end -->\n","protected":false},"excerpt":{"rendered":"<!-- google_ad_section_start -->\n<p>I&#8217;ve been hearing the term &#8220;water testing&#8221; for one of the work projects that I am involved in. \u00a0The term is used to describe the stage of the project when it&#8217;s available on the production servers with live data, but open only to a subset of the users. \u00a0After searching around for a bit, I &hellip; <a href=\"https:\/\/mamchenkov.net\/wordpress\/2013\/06\/11\/water-testing-is-not-a-term-for-software-testing\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Water testing is not a term (for software testing)<\/span><\/a><\/p>\n<!-- google_ad_section_end -->\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"_links_to":"","_links_to_target":""},"categories":[1,18,62],"tags":[243,3074,2962,1108,1588,17],"keyring_services":[],"class_list":["post-18349","post","type-post","status-publish","format-standard","hentry","category-general","category-programming","category-technology","tag-language","tag-quality-assurance","tag-terminology","tag-testing","tag-version-control","tag-work"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack-related-posts":[{"id":22107,"url":"https:\/\/mamchenkov.net\/wordpress\/2014\/07\/02\/qa-testing-tools-reviews-analysis-and-comparisons-of-quality-assurance-tools\/","url_meta":{"origin":18349,"position":0},"title":"QA Testing Tools &#8211; reviews, analysis, and comparisons of quality assurance tools","author":"Leonid Mamchenkov","date":"July 2, 2014","format":"link","excerpt":"QA Testing Tools - reviews, analysis, and comparisons of quality assurance tools","rel":"","context":"In &quot;All&quot;","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":21693,"url":"https:\/\/mamchenkov.net\/wordpress\/2014\/04\/24\/sauce-labs-selenium-testing-mobile-testing-javascript-unit-testing-and-more\/","url_meta":{"origin":18349,"position":1},"title":"Sauce Labs &#8211; Selenium Testing, Mobile Testing, JavaScript Unit Testing and More","author":"Leonid Mamchenkov","date":"April 24, 2014","format":"link","excerpt":"Sauce Labs - Selenium testing, mobile testing, JavaScript unit testing and more","rel":"","context":"In &quot;All&quot;","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":28540,"url":"https:\/\/mamchenkov.net\/wordpress\/2018\/05\/04\/unit-testing-the-big-picture\/","url_meta":{"origin":18349,"position":2},"title":"Unit Testing \u2013 The Big Picture","author":"Leonid Mamchenkov","date":"May 4, 2018","format":false,"excerpt":"\"Unit Testing \u2013 The Big Picture\" is a super useful for those of us who need a refresher or an overview of what software testing is in general, and how unit testing relates to other types of testing in particular.\u00a0 It covers a bit of history of testing, different approaches,\u2026","rel":"","context":"In &quot;All&quot;","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/mamchenkov.net\/wordpress\/wp-content\/uploads\/2018\/05\/V-Model-1-500x344.jpg?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":16567,"url":"https:\/\/mamchenkov.net\/wordpress\/2012\/07\/25\/wordpress-codex-automated-testing\/","url_meta":{"origin":18349,"position":3},"title":"WordPress Codex : Automated Testing","author":"Leonid Mamchenkov","date":"July 25, 2012","format":"link","excerpt":"WordPress Codex : Automated Testing","rel":"","context":"In &quot;All&quot;","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":21825,"url":"https:\/\/mamchenkov.net\/wordpress\/2014\/05\/17\/jest-painless-javascript-unit-testing\/","url_meta":{"origin":18349,"position":4},"title":"jest &#8211; painless JavaScript unit testing","author":"Leonid Mamchenkov","date":"May 17, 2014","format":"link","excerpt":"jest - painless JavaScript unit testing","rel":"","context":"In &quot;All&quot;","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":18239,"url":"https:\/\/mamchenkov.net\/wordpress\/2013\/05\/27\/ua-testing-with-selenium-and-phpunit\/","url_meta":{"origin":18349,"position":5},"title":"UA Testing with Selenium and PHPUnit","author":"Leonid Mamchenkov","date":"May 27, 2013","format":"link","excerpt":"UA Testing with Selenium and PHPUnit","rel":"","context":"In &quot;All&quot;","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"jetpack_sharing_enabled":true,"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/posts\/18349","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/comments?post=18349"}],"version-history":[{"count":0,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/posts\/18349\/revisions"}],"wp:attachment":[{"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/media?parent=18349"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/categories?post=18349"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/tags?post=18349"},{"taxonomy":"keyring_services","embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/keyring_services?post=18349"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}