Smoke Testing vs Sanity Testing

by Nataliia Vasylyna | February 20, 2017 6:10 am

Sanity testing is conducted after a build with fixed bugs and modified code is received. Its aim is to make sure that the functionality operates properly. This software testing type does not provide a thorough and detailed checking. It just verifies the work of new features or the removal of detected bugs.

In its turn, smoke testing ensures that the critical functionality operates correctly. It is conducted before regression testing[1] and detailed functional testing. For example, a new application is designed and before proceeding to its thorough testing procedure, the specialists check whether the launching process is successful, its GUI is responsive, etc.

What is the difference between smoke and sanity testing?

In other words, smoke testing is a general health examination and sanity testing – specialized health examination. They both can be performed manually and with the help of automated test scripts. Smoke testing is sometimes called build verification checking.

Learn more from QATestLab

Related Posts:

Endnotes:
  1. regression testing: https://qatestlab.com/services/step-by-step/regression-testing/
  2. Smoke Testing: What, Why & When: https://blog.qatestlab.com/2020/11/03/smoke-testing-what-why-when/
  3. Testing at a Complex Project: QATestLab Real Case: https://blog.qatestlab.com/2019/09/03/complex-project-testing/
  4. Sanity Testing vs Regression Testing: https://blog.qatestlab.com/2015/12/14/sanity-regression-testing/

Source URL: https://blog.qatestlab.com/2017/02/20/smoke-sanity-testing/