Wherever you are, you can help Ukraine

Act Now! Flag Ukraine

Smoke and Sanity Software Testing. What Is The Difference?

TestFortExpert by TestFortExpert on 02/27/2012

Smoke and Sanity Software Testing. What Is The Difference?

At first, let’s make out what smoke and what sanity testing is.

Smoke testing is non-exhaustive software testing, checking out whether the most important functions of a program work, but ignoring finer details. It is kind of testing performed to make sure that the project done can be further tested more thoroughly. It is done, in most cases, to inspect the stability of the build made for software testing.

Sanity testing also called acceptance testing is used to assess if the supplied build can be tested or not, that is to say sanity testing is application testing to check whether it is stable enough for further testing. A subset of regression test cases are performed to check if the software bugs or other issues were repaired and no other software bug is present after the changes. Occasionally when repeated cycles of regression testing are performed, sanity testing can be shifted for further stage, when all regression test cycles are finished. If a build is moved from staging testing server to production server, sanity testing of the software application is performed to test whether the build is sane enough to proceed further with production server or not.

So, what is the difference between them?

While smoke testing is applied to all areas of testing the software application, not too deep, though, and is considered to be a wide approach, sanity testing is a narrow regression testing, focusing on one small set of functionality areas of the software application.

To request a quote for software testing services visit Testfort website.

We use cookies to ensure your best experience. By continuing to browse this site, you accept the use of cookies and "third-party" cookies. For more information or to refuse consent to some cookies, please see our Privacy Policy and Cookie Policy