sanity testing

Smoke and Sanity Software Testing. What Is The Difference?

sanity testingAt 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 testing of an application 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.

  • Test cases for smoke testing are either manual or automated, but sanity testing is usually performed without any test scripts or cases.
  • The main aim of the smoke testing is to make sure if the main functions of the software application are working or not. While performing this test, finer details are not interested to us. Yet sanity testing is a superficial software testing type. It is performed every time a quick round of testing can check that the software application is performing in accordance with functional or other requirements.
  • Smoke testing of the software is performed to ensure if the build can be accepted for through software testing. However sanity testing is used to check if the requirements are met or not.

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


TestFort Blog

About TestFort Blog

TestFort blog is an official blog of TestFort QA Lab company and is dedicated to various QA and software testing issues.


  1. March 2, 2012 @ 9:58 am QA Thought Leaders

    Thank you for sharing this post. I find this very informative. Can you please confirm if we get new features included every week what is applicable Smoke testing, Sanity Testing or both, I am talking purely about Retail segment and its QA Testing. Look forward to your response.

    • May 3, 2012 @ 2:08 am Damin

      Whats up, I desired to ask you some thing. Is this a wrorpdess blog? My business is wondering about changing our website from Blogger to wrorpdess, ya think that is feasible? Also did you create this specific theme yourself some how? Cheers for your assistance!

  2. May 19, 2012 @ 6:22 pm software,programs,affiliat,windows

    Hi there, simply was alert to your weblog via Google, and found that it’s really informative. I’m going to watch out for brussels. I will appreciate when you proceed this in future. Many folks will probably be benefited from your writing. Cheers!

  3. January 30, 2013 @ 7:19 pm Melissa

    Smoke and Sanity Testing are defined as the same in the ISTQB glossary and Acceptance Testing is defined as: Formal testing with respect to user needs, requirements, and business
    processes conducted to determine whether or not a system satisfies the acceptance criteria
    and to enable the user, customers or other authorized entity to determine whether or not to
    accept the system

Would you like to share your thoughts?

Images are for demo purposes only and are properties of their respective owners.
Old Paper by © 2018