In this tutorial, we are going to study about sanity testing. Like smoke testing, sanity testing is also one of the most confused term in software testing. At the end of the post, you can also refer to the recommended reading section, where you will learn about smoke testing and difference between smoke and sanity testing.
Sanity testing definition
Sanity testing is the subset of regression testing. Like regression, in case of sanity testing, we check if a fix has not affected the other working functionalities of the application but in a lesser time and with lesser number of test cases.
So, basically we perform sanity testing after receiving a fix (usually a minor fix). We check limited but critical part of functionality and then decide as to whether further testing is required or not.
Some salient features of sanity testing
- Subset of regression testing – It is subset of regression testing and focuses on smaller section of the application.
- Narrow and deep – It is narrow and deep approach of testing, where in we cover limited functionality deeply.
- Not documented and automated – Most of the times sanity tests are undocumented and unscripted.
Advantages of sanity testing
- It helps in quickly identifying issues in the core functionality.
- Since, no documentation is required for sanity testing, these can be carried out in lesser time.
- In case of issues found during sanity testing build is rejected thus saving time for execution of regression tests.