Testing the basic and critical features of an application before proceeding with deep rigorous testing is known as Smoke Testing.
In Smoke Testing we only test the positive flow of basic and critical features of the application, generally it is done to make sure that build is testable.
Since in Smoke Testing we verify or check if the build is testable or not it is also known as Build Verification Testing(BVT).
Why Smoke Testing?
To delete the blocker bugs in early stage we go for Smoke Testing so that the test engineer does not sit idle and to test whether the application is testable or not and also developer will get enough time to analyze the bug, in Smoke Testing we test basic and critical features of the application i.e, we test only for positive values.
Types of Smoke Testing:
Formal Smoke Testing.
Informal Smoke Testing.
Formal Smoke Testing
When it is intimated by team lead to do Smoke Testing, it is called as formal Smoke Testing.
Informal Smoke Testing
When it is not intimated by team lead to do Smoke Testing, it is always a good approach to start testing with Smoke Testing.
Advantages of Smoke Testing
It is a time saving approach where the blocker bug can be detected at very early stage.
The developer get enough time to analyze and fix the bugs.
Test engineer will not be blocked with their testing and smoothly they can proceed with testing the application.