Smoke testing, the preliminary level of testing is done to ensure whether the major functionalities of a build/software is functioning properly. In simpler words, we can say that it is an entry criteria for ensuring that a software is ready for further testing. Confidence testing, Build Verification Testing are other names for smoke testing. In this type of testing, testers execute test cases based upon the requirement mainly the positive cases. The main functionalities, work flows etc will be tested first.
Testers can prepare a smoke testing checklist/document and pass to developers prior to the start of testing. The checklist or the document should include the test cases which are going to be executed while performing smoke testing. Testers may also include requirement id against each test cases as well a comment section to specify the pass or fail status of the cases. By passing the checklist developers can also ensure that the major functionalities are implemented. A simple checklist can be as below:
Smoke testing checklist
|Requirement ID:||Test case or test scenarios||Comment (Pass/Fail)|
By passing the checklist to developers, it can be useful for them to execute those cases while performing their unit testing. Hope you have understood the importance of smoke testing. Let's ensure that there are no more early smoke and fire:).