What is sanity testing in QA

by
What is sanity testing in QA

Sanity testing is a type of software testing performed after receiving a software build, with minor changes in code or functionality, to ascertain that the bugs have been fixed and no further issues are introduced due to these changes. It is a subset of regression testing often used as a checkpoint to determine if testing should proceed further.

Characteristics of sanity testing

  • It focuses on specific functionality rather than the entire system.
  • Often performed without formal test cases, relying on the tester’s system knowledge.
  • It doesn’t involve deep testing but checks if the essential functions work as expected.
  • It helps quickly determine if a build is stable enough for further testing.
  • Used to decide whether to proceed with more comprehensive testing or reject the build.
  • It doesn’t aim to test every feature but focuses on core functionality.
  • It helps identify obvious issues early in the testing process.
  • Provides quick assurance that the essential functions are working.

When to perform sanity testing

  • After receiving a new build with minor changes
  • When there’s limited time for thorough testing
  • Before starting full regression testing
  • After fixing a specific bug to ensure the fix works and doesn’t break other functionalities.
  • During the later stages of the development cycle, when frequent builds are received.

Benefits of sanity testing

  • Saves time and resources by quickly identifying major issues
  • Helps in the early detection of defects
  • Increases confidence in the build’s stability
  • Allows testers to provide quick feedback to developers
  • Reduces the risk of proceeding with further testing on an unstable build

You may also like following the articles below

While sanity testing is an integral part of the QA process, it should be noted that it doesn’t replace more comprehensive testing methods. It should be used with other testing types to ensure overall software quality.