Difference between Smoke and Sanity Testing?

Smoke Testing:
  1. Smoke testing is done to check the normal health of the build and make sure if it is possible to continue testing. It is done in the beginning of the software testing cycle.
  2. Smoke testing is conducted on early builds to ascertain application most critical features are working and its ready for complete testing
  3. The objective of Smoke testing is to check the application stability before starting the thorough testing
  4. It follows shallow and wide approach where you cover all the basic functionality of the software.
  5. Smoke testing is like general health checkup where all application critical areas are tested without going into their details (build verification)
Sanity Testing
  1. Sanity testing is done after thorough regression testing is over, it is done to make sure that any defect fixes or changes after regression testing does not break the core functionality of the product. It is done towards the end of the product release phase.
  2. Sanity testing is conducted on stable builds (after multiple regression tests) to ascertain new functionality/ bugs have been fixed and application is ready for complete testing
  3. The objective of Sanity testing is to check the application rational before starting the thorough testing
  4. Sanity testing follows narrow and deep approach with detailed testing of some limited features.
  5. Sanity testing is like specialized health checkup where small area of the application is thoroughly tested



To receive daily posted JOBS & Interview Questions
Just enter your email address below and click 'Submit'
Enter your email address:

Make sure to activate your subscription by clicking on the activation link sent to your email