After sharing information on Smoke testing in the previous articles, in today’s Software testing class I am explaining about the Sanity testing. In this post I will explain the What is a sanity testing, definition and tips on this testing.
What is a Sanity Testing?
After receiving a Software build with the minor issues fixes in code or functionality, this testing is carried out to check whether the bugs reported in previous build are fixed & there is regression introduced due to these fixes i.e. not breaking any previously working functionality. The main aim of this testing to check the planned functionality is working as expected. Instead of doing whole Regression testing definition this testing is performed.
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.
After completion of regression testing the this 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 nearing end of SDLC i.e. while releasing the software. You can say that this testing is a subset of acceptance testing. We can also say Tester Acceptance Testing for Sanity testing. Such testing is narrow & deep approach of testing, it needs to concentrate limited & main features of testing in detailed.
Here are the few consolidated points:
- It follows narrow and deep approach with detailed testing of some limited features.
- It is typically non-scripted.
- It is a sub-set 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 is to check the after minor fixes the small section of code or functionality is working as expected & not breaking related functionality.
Hope you get clear idea of Sanity testing in the above article & cleared confusions on Sanity testing.
If you like this article then please share this article over your friends. And don’t forget to join the conversation below to share your best testing tips!
28 thoughts on “Sanity Testing”
Hi, I am fresher in software testing & this is a fantastic new website & good way to present the posts.
Thank you sir.
I like this blog very much, Its a nice sanity testing info to read and incur information.
Very nice explanation…. Thanks for writing
Wonderful blog of software testing, really help a lot for understanding concepts of Software testing!
I really liked this explanation…. and hope it will take me to right direction…..
Thank you
i am very confused in sanity testing some say’s that this testing is done before in
testing and some say’s it is done at the end …then who is right.because this guy’s are also tester in company…..
There is a typo “SLDC” written instead of “SDLC” i.e. Software Development Life Cycle.
Corrected the typo, Thanks Dattatray!!!
very very useful site ,I put it in my favorite thx and keep up
its nice.. this site helping to many people.. i would like to suggest on thing …. if u take one example for every concept like gmail or yahoo page.. can understand clearly i think..
I like this blog very much, Its a NICE sanity testing info to read and incur information
It would had been good if there was an example explaining this in detail.Anyways nice explanation.
very very useful site ,I put it in my favorite thx and keep it up
Very very useful site, i would like to suggest on thing …. if u take one example for every concept
You are doing great work by sharing your knowledge.
can you explane me what is basic need smoke testing??
Hi i am fresher this blog is very nice to understand things related to testing great job keep up…i like this blog very much
Please explain difference between Sanity and Regression testing ?
Hi, i’m chiranjeevi you are mentioned sanity test is subset of acceptance test but it’s a subset of regression test.am i right?
IT’S Really helps me to understand
Sanity testing is the sub-set of Acceptance testing or Regression testing or both, i’m just confuse can you please explain me about this.
I really liked this explanation. Thank you
Very informative… thanks for providing.
Anyone can reply -can we say – retesting and regression together as sanity testing.
hi in the smoke testing as you explained in smoke sanity testing diagram after sanity test passes then we do regression and functional testing. but in sanity testing you are telling after regression we go go for sanity. I am not understanding
After reading more about Sanity testing over internet, I am now a bit confused. What is this regression testing?
@Doris, Regression testing is type of testing carried out to ensure that changes made in the fixes or any enhancement changes are not impacting the previously working functionality. It is executed after enhancement or defect fixes in the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle.
@Gaurav, @chiranjeevi, @Ram –
Sanity testing is considered as a subset of regression testing.
Sanity testing is performed only when testers do not have enough time for testing. Regression testing perform when enough time is available.
Sanity testing is surface level testing and regression is not.
Regression testing can be carried out using tool but sanity is not.
Not complete test cases are executed in Sanity testing, but regression testing needed complete test case execution.
Sanity testing cannot be carried out using script, but regression can be carried out by scripts.