top button

What is a Sanity Testing?

+2 votes
103 views
posted Sep 21, 2018 by Arunkumaarts

Share this question
Facebook Share Button Twitter Share Button Google+ Share Button LinkedIn Share Button Multiple Social Share Button

4 Answers

0 votes

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 Sanity testing to check the planned functionality is working as expected. Instead of doing whole regression testing the Sanity testing 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 upon 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, it needs to concentrate limited & main features of testing in detailed.

answer Sep 21, 2018 by Bharath
0 votes

Its a subset of regression testing and it is performed when we have not enough time for doing testing. Sanity testing is the surface level testing where QA engineer verifies that all the menus, functions, commands available in the product and project are working fine. Its performed after receiving a software build . Main Purpose of sanity testing is to determine that the proposed functionality works roughly as expected.

answer Sep 25, 2018 by Navita
0 votes
answer Sep 25, 2018 by Sakthi Kandan
0 votes

Sanity testing is a kind 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. The goal is to determine that the proposed functionality works roughly as expected. If sanity test fails, the build is rejected to save the time and costs involved in a more rigorous testing.

The objective is "not" to verify thoroughly the new functionality, but to determine that the developer has applied some rationality (sanity) while producing the software.

answer Oct 26, 2018 by Bhumika Prajapati
...