Smoke testing

Smoke Testing Smoke testing, also known as build verification testing, is performed on initial builds before they are released for extensive testing. The idea is to net issues, if any, in the preliminary stages so that the QA team gets a stable build for testing, thus saving a significant amount of effort and time spent by the QA

What is smoke testing?

• Smoke testing is non-exhaustive and focuses on testing the workflow of the software by testing its critical functionalities. The test cases for smoke testing can be picked up from an existing set of test cases. The build is marked rejected in case it fails the smoke tests.

Smoke Testing vs Sanity Testing

• Let us examine Smoke and Sanity testing • Smoke testing essentially checks for the stability of a software build. It can be deemed as a preliminary check before the build goes for testing.

• Sanity testing is performed after a stable build is received and testing has been performed. It can be deemed as a post-build check, to make sure that all bugs have been fixed. It also makes sure that all functionalities are working as per the expectations.

• Read More about Smoke Testing vs Sanity Testing