What is Sanity Testing & Sanity Definition?
After receiving a Software build with the minor issues fixes in code or functionality, Sanity Testing is carried out to check whether the bugs reported in the previous build are fixed & there is a regression introduced due to these fixes, i.e. not breaking any previously working functionality. The main aim of the Sanity test to check the planned functionality is working as expected. Instead of doing whole regression testing, the Sanity test is performed.
- Sanity tests help to avoid wasting time and cost involved in testing if the build is failed. The tester should reject the build to build failure.
- After completion of regression testing, the Sanity testing is started to check the defect fixes & changes done in the software application is not breaking the core functionality of the software. Typically this is done near the end of SDLC, i.e. while releasing the software. You can say that sanity testing is a subset of acceptance testing. We can also say Tester Acceptance Testing for Sanity testing. Sanity testing is a narrow & deep approach to testing, and it needs to concentrate limited & main features of testing in detailed.
Read Also: Different Agile (Scrum) Practices and Role
How to Do Sanity Testing?
Here are the few consolidated points of Sanity testing:
- It follows a narrow and deep approach with detailed testing of some limited features.
- It is typically non-scripted.
- It is a subset of regression testing.
- It is cursory testing to prove software application is working as mention in the specification documents & meets the user needs.
- It is used to verify the requirements of end-users are meeting or not.
- It to check the after minor fixes the small section of code or functionality is working as expected & not breaking related functionality.
In this post, we are sharing about sanity test and also discuss various topics like sanity check, sanity test, what is sanity.