Sanity testing vs Smoke testing

www webomates.com 1 Sanity testing vs 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

 Sanity testing is performed on a stable build which represents minor changes in code/functionality to ensure that none of the existing functionality is broken due to the changes.

 For this, a subset of regression tests is conducted on the build

Turn static files into dynamic content formats.

Create a flipbook

Sanity testing vs Smoke testing

Published on Oct 25, 2021

Webomates INC

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.Sanity testing is performed on a stable build which represents minor changes in code/functionality to ensure that none of the existing functionality is broken due to the changes. For this, a subset of regression tests is conducted on the build.On comparing sanity testing vs smoke testing we can say that Smoke testing takes care of building stability before any other comprehensive testing (including sanity testing) can be performed whereas, sanity testing is performed on a stable build, which has passed the acid test of smoke tests and another testing

Issuu converts static files into: digital portfolios, online yearbooks, online catalogs, digital photo albums and more. Sign up and create your flipbook.