Software Testing plays a vital role in software development and release. There are different types of software testing each of them has a unique purpose for the software development process. Sanity testing is one of the most useful tests among them.
It is a kind of Software Testing to ensure the bugs are fixed and not have further issues due to the changes. It is a type of retesting to ascertain whether the changes or newly added functionalities work as expected. The process of sanity testing is not about detailed testing, it is to validate the functionality of the application. It is generally used for critical bug fixes. It is performed to ensure the working of new code modifications. The aim is not to verify the critical features of the application but to validate whether the bugs are fixed or not. It usually performs after receiving a minor fix.
It is a kind of regression testing with a focus on a few impacted functionalities only.
It will be carried out whenever the tester receives a software build with minor issue fixes in code or functionality.
It is performed after successful regression testing. It doesn’t have any rules to carry out tests.
We should identify the functionalities along with the modifications introduced in the code at first. Next, verify the implemented functionalities working as expected specifications. Then the tester should randomly test and ensure all the functionalities and changes working fine.
After successful sanity testing, the system can be passed for thorough testing.
Imagine a scenario of an application you have with multiple modules. You have a login page form that allows the user to enter the data and login. Now there is a new requirement from the user which is to add the “Forgot Password” button in the login page that enables him to find or create his password again.
The development team applies the requirement and sends the application for sanity testing. At first, you have to perform basic tests on the newly added feature “Forgot Password”. Then you have to check the newly added feature doesn’t affect the existing features, i.e., check if the other functionalities and features of the login page are still working fine.
If the application finds no issues, it can be subject to further testing. If it is not, the application should be rejected.
In Simple, Sanity testing is a checkpoint to determine if further testing can proceed or not. It determines that the required functionalities work roughly as expected. Although testers use sanity testing as a decision criterion for accepting or rejecting the software. Sanity testing is important because it saves time if any issue is identified by checking it quickly.
In a nutshell, the main aim of sanity testing is to ensure the functionality of the software even after many iterations of regression are carried out. Thus, it increases the confidence to release software.