What is Smoke Testing?

The term comes from the hardware testing, in the hardware testing initial pass is done to check if it did not catch the fire or smoke in the initial switch on.

Define Software & Smoke Testing

Prior to start Smoke testing few test cases need to created once to use for smoke testing. These test cases are executed prior to start actual testing to check critical functionalities of the program is working fine.

This set of test cases written in such a way that all functionality is verified but not in deep. The objective is not to perform exhaustive testing, the tester needs to check the navigation’s & adding simple things, the tester needs to ask simple questions

• Can tester able to access software applications?
• Does the user navigate from one window to the other?
• Check that the GUI is responsive” etc.
• The test cases can be executed modafinil online manually or automated; this depends upon the project requirements. In this type of testing mainly focus on the important functionality of the application, the tester does not care about the detailed testing of each software component, this can be cover in the further testing of the application.
• The Smoke testing is typically executed by testers after every build is received for checking the build is in a testable condition.
• This type of testing is applicable in the Integration Testing, System Testing and Acceptance Testing levels.

Advantages of Smoke testing

• It helps to find issues introduced in the integration of modules.
• It helps to find issues in the early phase of testing.
• It helps to get the confidence to a tester that fixes in the previous builds not breaking major features (of course, only features exercised by smoke testing