over 9 years ago
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).
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.
When it is intimated by team lead to do Smoke Testing, it is called as formal 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.
Can you help out the community by solving one of the following Manual Testing problems?
Do activity (Answer, Blog) > Earn Rep Points > Improve Rank > Get more opportunities to work and get paid!
For more topics, questions and answers, please visit the Tech Q&A page.
0 Comment(s)