...smoke test?Can u send me a case study of smoke test

<< Back to: comp.software.testing Frequently Asked Questions (FAQ)

Answer by Charles Nichols
Submitted on 8/2/2003
Rating:	Rate this answer:
I first encountered the phrase twenty-some years ago while working for an Aerospace company. When an avionic system was turned on for the very first time it was called a "Smoke Test." Smoke being a not uncommon result of an electrical short circuit. ;-) In software, the term commonly refers to a narrow set of tests which determines if more extensive testing of the product is warranted. The emphasis is on brevity, and should not take more than a few minutes to run. For example, in an OOP framework, one might instantiate an object from each class in the End User API and arbitrarily invoke a single method from each. I'm not aware of any "case studies" on the subject but I did give the above explanation to a newly hired software project manager who replied "What does instantiate an object mean." I resigned that same week.

Answer by Sanjay A.V
Submitted on 8/24/2005
Rating: Not yet rated	Rate this answer:
Smoke testing is non-exhaustive software testing, ascertaining that the most crucial functions of a program work, but not bothering with finer details. The term comes to software testing from a similarly basic type of hardware testing, in which the device passed the test if it didn't catch fire the first time it was turned on. A daily build and smoke test is among industry best practices advocated by the IEEE (Institute of Electrical and Electronics Engineers). The original version of smoke testing predates both hardware and software testing and is still used to test the integrity of a variety of systems by placing a smoke bomb inside some kind of a chamber to see if there are any leaks for the smoke to escape through.

Answer by Viqar Qadir
Submitted on 11/22/2006
Rating: Not yet rated	Rate this answer:
Also called a "Build Acceptance" test, a "Smoke Test" verifies that a software released as a new build or after a major fix is in a stable enough condition to withstand further, often more stressful, testing. A smoke test achieves this verification by performing a set of tests that is more wide than deep. The normal verifications for such tests include the application initiates, menu items and buttons respond, essential components of the system are present etc. The term originated from electronics testing where if a component failed (in the old days of diode and triode tubes)there was actual smoke to be seen...and as they say "where there's smoke, there's a fire" The same term is also used for testing plumbing where smoke is forced through plumbing to see if there are leaks before forcing actual water through it. In type setting in the printing business a new type letter is sometimes held over candle smoke and then pressed against paper to see if it prints correctly. However, it is only in the software industry that a smoke test is referring to metaphorical smoke. Another important thing to keep in mind is that a smoke test is not a sanity test. Where a smoke test is wide and shallow in it's scope, a sanity test focuses mostly on a single check for a formula or a calculation.

Answer by Ranjeet Sinha
Submitted on 5/29/2007
Rating: Not yet rated	Rate this answer:
In software, the term smoke testing describes the process of validating code changes before the changes are checked into the product�s source tree. After code reviews, smoke testing is the most cost effective method for identifying and fixing defects in software. Smoke tests are designed to confirm that changes in the code function as expected and do not destabilize an entire build. Smoke testing is done by developers before the build is released or by testers before accepting a build for further testing. In software engineering, a smoke test generally consists of a collection of tests that can be applied to a newly created or repaired computer program. Sometimes the tests are performed by the automated system that builds the final software. In this sense a smoke test is the process of validating code changes before the changes are checked into the larger product�s official source code collection. Next after code reviews, smoke testing is the most cost effective method for identifying and fixing defects in software; some even believe that it is the most effective of all.

Answer by ajjain
Submitted on 6/12/2007
Rating: Not yet rated	Rate this answer:
� In plumbing, a smoke test forces actual smoke through newly plumbed pipes to find leaks, before water is allowed to flow through the pipes. � In woodwind instrument repair, a smoke test involves plugging one end of an instrument and blowing smoke into the other to test for leaks. (This test is no longer in common use) � In electronics, a smoke testing is the first time a circuit is attached to power, which will sometimes produce actual smoke if a design or wiring mistake has been made. � In computer programming and software testing, smoke testing is a preliminary to further testing, which should reveal simple failures severe enough to reject a prospective software release. In this case, the smoke is metaphorical. Next after code reviews, smoke testing is the most cost effective method for identifying and fixing defects in software; some even believe that it is the most effective of all. In software testing, a smoke test is a collection of written tests that are performed on a system prior to being accepted for further testing. This is also known as a build verification test. This is a "shallow and wide" approach to the application. The tester "touches" all areas of the application without getting too deep, looking for answers to basic questions like, "Can I launch the test item at all?", "Does it open to a window?", "Do the buttons on the window do things?". There is no need to get down to field validation or business flows. If you get a "No" answer to basic questions like these, then the application is so badly broken, there's effectively nothing there to allow further testing. These written tests can either be performed manually or using an automated tool. When automated tools are used, the tests are often initiated by the same process that generates the build itself. It verifies the major functionality at high level in order to determine if further testing is possible. The Smoke test scenarios should emphasize breadth more than depth. All components should be touched, and every major feature should be tested briefly. If test fails, the build is returned to developers untested.

FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

<< Back to: comp.software.testing Frequently Asked Questions (FAQ)

[ Home | FAQ-Related Q&As | General Q&As | Answered Questions ]

Question by usha
Submitted on 7/7/2003
Related FAQ: comp.software.testing Frequently Asked Questions (FAQ)
Rating:	Rate this question:
What is smoke test?Can u send me a case study of smoke test

Answer by forrest
Submitted on 7/11/2003
Rating:	Rate this answer:
here's a start http://urchin.earth.li/cgi-bin/twic/wiki/view.pl?page=SmokeTest

Answer by Siva Kaza
Submitted on 7/24/2003
Rating:	Rate this answer:
It verifies the major functionality at high level in order to determine if further testing is possible. The Smoke test scenarios should emphasize breadth more than depth. All components should be touched, and every major feature should be tested briefly. If test fails, the build is returned to developers un-tested.

Answer by sanil
Submitted on 8/12/2003
Rating:	Rate this answer:
Smoke Test is covering all the functionality in less time to make sure that the application works fine in the normal condition. Smoke test is done during the daily build.

Answer by S. Datta Ramprasad
Submitted on 9/8/2003
Rating:	Rate this answer:
It is the cousin brother of Sanity Testing !

Answer by SHYAM SUNDAR
Submitted on 9/16/2003
Rating:	Rate this answer:
A rudimentary form of testing applied to electronic equipment following repair or reconfiguration, in which power is applied and the tester checks for sparks, smoke, or other dramatic signs of fundamental failure. 2. By extension, the first run of a piece of software after construction or a critical change.

Answer by Horney
Submitted on 9/17/2003
Rating:	Rate this answer:
Sanity test or Smoke test are subsets of the confidence test and are used only to validate high-level functionality.

Answer by vasu
Submitted on 1/16/2004
Rating:	Rate this answer:
if u can smell, great, u did the smoke testing. cheers.

Answer by MANOJ KATIYAR
Submitted on 2/9/2004
Rating:	Rate this answer:
SMOKE TEST IS TEST OF LAMINARITY OF THE LAMINAR AIR FILTER INSTALLED IN CLEAN ROOMS.

Answer by Suresh
Submitted on 4/12/2004
Rating:	Rate this answer:
Access my existing account

Answer by sankar
Submitted on 6/1/2004
Rating:	Rate this answer:
smoke is the initial level of testing effort to determine if the new software version is performing well enough for its major level of testing effort

Answer by Abdul
Submitted on 6/2/2004
Rating:	Rate this answer:
Also known as "Confidence Testing". The top level functionalities should work fine.

Answer by k.haribaskar
Submitted on 6/23/2004
Rating:	Rate this answer:
smoke testing is similar to sanity testing A QUICK-AND-DIRTY test that the major functions of piece of software work.

Answer by kiran
Submitted on 6/29/2004
Rating:	Rate this answer:
It is a integration testing technique to check the functionality,architecture of the system for conformance

Answer by Bis
Submitted on 7/2/2004
Rating:	Rate this answer:
Sanity test and smoke test go hand in hand ..

Answer by Gopal Karanam
Submitted on 7/15/2004
Rating:	Rate this answer:
High Level Functional Testing, an Initial stage of Complete Testing.

Answer by Basavanagowda.C.G
Submitted on 10/8/2004
Rating: Not yet rated	Rate this answer:
smoke testing is the testing of basic functionality of the project. if this basic functionality itself is not working then there is no meaning in testing of the other functionalities in that project. for ex if we take a log in window, the basic functionality of this log in is 'it should allow the user for valid user name & valid pass word' if this itself is not working then there is no meaning in testing it for invalid user name & valid password, invalid UN & invalid PWD, valid UN & invalid PWD, valid UN & valid PWD but not valid combination (i.e.. X person's valid UN & Y person's valid PWD, blank in UN field & valid PWD, ,,,,,,,

Answer by ramalakshman kanduri
Submitted on 10/29/2004
Rating: Not yet rated	Rate this answer:
Smoke Test is one of the type of Testing. When we are cheking the application functtionality overview through context level not indepth(detailed level). Simply we can say general inspection of the testing.

Answer by Vel
Submitted on 12/13/2004
Rating: Not yet rated	Rate this answer:
Testing the Major Functionalities in such a way to check whether the product functions correctly without getting struck at any point.

Answer by mohangowda
Submitted on 12/17/2004
Rating: Not yet rated	Rate this answer:
understanding the major efects,when u make action to particular event thoroly , when u r testing

Answer by qaz
Submitted on 12/23/2004
Rating: Not yet rated	Rate this answer:
this is not a testing it is a debugging practcies

Answer by Dakshina Balijepalli
Submitted on 1/19/2005
Rating: Not yet rated	Rate this answer:
When a new version is added to the application, end to end flow testing done checking to make sure that it works well with present working application. Done during day to day testing process.

Answer by revzum
Submitted on 3/1/2005
Rating: Not yet rated	Rate this answer:
The Smoke testing is an integration testing approach that is commonly used when "Shrink wrapped" software items are being produced.

Answer by B. VIJAY
Submitted on 3/4/2005
Rating: Not yet rated	Rate this answer:
Smoke testing is the process of testing carried out to prove the application does not work. It is the initial level test.

Answer by Ravi
Submitted on 7/2/2005
Rating: Not yet rated	Rate this answer:
Smoke testing is an integration testing approach that is commonly used when "shrink wrapped" software products are being developed.

Answer by Vikram
Submitted on 7/20/2005
Rating: Not yet rated	Rate this answer:
Smoke testing is the testing in which through components, we will Test the memory Leakage.

Answer by Vishakha
Submitted on 7/25/2005
Rating: Not yet rated	Rate this answer:
A smoke test is a series of test cases that are run prior to commencing with full-scale testing of an application. The idea is to test the high-level features of the application to ensure that the essential features work. If they do not work, there is no need to continue testing details of the application, so the testing team will refuse to do any additional testing until all smoke test cases pass. This puts pressure on the development team to ensure that the testing team does not waste valuable testing time with code that is not ready to be tested.

Answer by Prakash Ramasamy
Submitted on 7/27/2005
Rating: Not yet rated	Rate this answer:
If there is no sufficient time for through testing we have to perform the smoke test. In this test we have to check important or High level functionalities only. If test fails we have to return the build to Developer team.

Answer by Navdeep
Submitted on 7/30/2005
Rating: Not yet rated	Rate this answer:
Smoke testing is the testing of Basic function and checking whether the system is working corectly or not without going into the details.

Answer by Axsys kishore
Submitted on 8/9/2005
Rating: Not yet rated	Rate this answer:
smoke testing is the basic functionality testing before doing fullfledge of testing.If we are satisfied with smoke testing then it will allowed for further testing,if not sent back to the developers.

Answer by AzHaR MeHmOoD
Submitted on 8/18/2005
Rating: Not yet rated	Rate this answer:
Checking Major Functionalites according to SRS is Smoke Testing

Answer by ramakesava reddy
Submitted on 8/18/2005
Rating: Not yet rated	Rate this answer:
The general definition (related to Hardware) of Smoke Testing is: Smoke testing is a safe harmless procedure of blowing smoke into parts of the sewer and drain lines to detect sources of unwanted leaks and sources of sewer odors. It it is related to s/w, the definition is Smoke testing is non-exhaustive software testing, ascertaining that the most crucial functions of a program work, but not bothering with finer details.

Answer by gadde999
Submitted on 8/31/2005
Rating: Not yet rated	Rate this answer:
It describes an initial set of tests that determines a new version of application performs well enough for further tests

Answer by Ani
Submitted on 9/12/2005
Rating: Not yet rated	Rate this answer:
Smoke test is the best

Answer by ramya
Submitted on 9/17/2005
Rating: Not yet rated	Rate this answer:
smoke testing is then process of testing major functionalities of an application.

Answer by fdfdffdsfds
Submitted on 9/19/2005
Rating: Not yet rated	Rate this answer:
dsfdsfasdf