Thursday, March 12, 2009

Difference between Smoke Testing and Sanity Testing

This workflow detail is to validate that the build is stable enough for detailed test and evaluation effort to begin. This work is also referred to as a smoke test, build verification test, build regression test, sanity check or acceptance into testing. This work helps to prevent the test resources being wasted on a futile and fruitless testing effort.

There is no Big difference between Smoke Testing and Sanity Testing. But if we go in detail:-

Smoke Test:

When a build is received, a smoke test is run to ascertain if the build is stable and it can be considered for further testing.

Smoke testing can be done for testing the stability of any interim build.

Smoke testing can be executed for platform qualification tests.

Sanity testing:

Once a new build is obtained with minor revisions, instead of doing a through regression, a sanity is performed so as to ascertain the build has indeed rectified the issues and no further issue has been introduced by the fixes. Its generally a subset of regression testing and a group of test cases are executed that are related with the changes made to the app.

Generally, when multiple cycles of testing are executed, sanity testing may be done during the later cycles after through regression cycles.

To Read in Details with example click here


Software Development Company said...

Hello Saleem,
The Article on Difference between Smoke Testing and Sanity Testing give detailed information about it. Thanks for Sharing the information about brief on Smoke Testing and Sanity testing difference For More information check the detail on the Smoke testing here Mobile App Testing

Cracking the coding interview said...

Informative article. These differences helped me to understand the difference between smoke and sanity testing. Programming interviews often give testing related questions, cracking the coding interview seems daunting task. Keep sharing these educational blogs, looking forward for more.