Sanity Testing

Sanity testing, a software testing technique performed by the test team for some basic tests.

When there are some minor issues with software and a new build is obtained after fixing the issues then instead of doing complete regression testing a sanity is performed on that build. You can say that sanity testing is a subset of regression testing.

It is used to determine if the section of the application is still working after a minor change.

Sanity tests helps to avoid wasting time and cost involved in testing if the build is failed. Tester should reject the build upon build failure.

Sanity testing can be narrow and deep. Sanity test is a narrow regression test that focuses on one or a few areas of functionality.

Here are the few consolidated points of Sanity testing:


  • Sanity testing to check the after minor fixes the small section of code or functionality is working as expected & not breaking related functionality.
  • Sanity testing is typically non-scripted.
  • Sanity testing is a sub-set of regression testing.
  • Sanity testing follows narrow and deep approach with detailed testing of some limited features.
  • Sanity testing is cursory testing to prove software application is working as mention in the specification documents & meets the user needs.
  • Sanity testing to check the after minor fixes the small section of code or functionality is working as expected & not breaking related functionality.
Share This:
Facebooktwittergoogle_plusredditpinterestlinkedintumblr