

Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Smoke testing is an initial testing process to ensure software stability and readiness for further testing. Originated from hardware testing, it checks critical functionalities and navigation. Test cases can be manual or automated, focusing on important application functions. Smoke testing helps find issues early, ensures fixes don't break major features, and is applicable in integration, system, and acceptance testing.
Typology: Exercises
1 / 3
This page cannot be seen from the preview
Don't miss anything!


What is Smoke Testing? Smoke testing is the initial testing process exercised to check whether the software under test is ready/stable for further testing. The term ‘Smoke Testing’ is came from the hardware testing, in the hardware testing initial pass is done to check if it did not catch the fire or smoked in the initial switch
testing. These test cases are executed prior to start actual testing to checkcritical functionalities of the program is working fine. This set of test cases written such a way that all functionality is verified but not in deep. The objective is not to perform exhaustive testing, the tester need check the navigation’s & adding simple things, tester needs to ask simple questions “Can tester able to access software application?”, “Does user navigates from one window to other?”, “Check that the GUI is responsive” etc. Here are graphical representation of Smoke testing & Sanity testing in software testing:
Smoke Sanity Testing Diagram The test cases can be executed manually or automated; this depends upon the project requirements. In this types of testing mainly focus on the important functionality of application, tester do not care about detailed testing of each software component, this can be cover in the further testing of application. The Smoke testing is typically executed by testers after every build is received for checking the build is in testable condition. This type of testing is applicable in the Integration Testing, System Testing and Acceptance Testing levels.
It helps to find issues introduced in integration of modules. It helps to find issues in the early phase of testing. It helps to get confidence to tester that fixes in the previous builds not breaking major features (off course, only features exercised by smoke testing).