Sanity Testing: Sanity Testing is a part of Regression testing . It is performed by the test team to do some basic testing when they don’t have enough time to test the whole application. It is used to determine if all the features and functionality of an application is still working fine after a minor change or not. Sanity testing is performed to make sure that all the errors or bugs have been removed and there are no more issues introduced due to recent changes made within an application. It is performed when Smoke testing is done , accepted by Q&A team for further testing and verifies the major functionality with finer details.
It is usually unscripted and helps to identify the dependent missing functionality. It is narrow and deep testing that focuses on one or a few areas of functionality. When there are some minor issues within the software and a new build is obtained after fixing the issues then instead of doing complete regression testing sanity is performed on that build. Sanity testing helps to avoid the wastage of time and cost if the build is failed. Sanity testing helps to check that after minor fixes done in a small section of code, the functionality is working as expected & not breaking related functionality .
When we Perform Sanity Testing?
Sanity testing is performed when development team needs to know quick state of the product after they have done changes in the code or there is some controlled code change in a feature to fix any critical issue, and stringent release time-frame does not allow complete regression testing.
Importance of Sanity Testing
1. Sanity testing makes the tester confident about the functionality of an application.
2. Sanity testing assures that the part of the system or methodology works roughly as expected.
3. Using sanity testing the testers makes sure that the basic functionality of an application is working fine and the proposed functionality works roughly as expected.
4. By performing sanity testing on a Mobile Device Testing will be sure that the application will be working fine on other mobile devices having the same operating system.
5. Sanity testing is not documented and thus it saves time and is easy to perform.
6. Sanity testing gives a rough idea of the functionality of the application and the number of uncertainties in the application due to bug fixes.
7. Sanity testing is beneficial when the time for a particular project is limited and tester has already checked the project in detail.
8. Sanity testing does not require many testers and thus saving testing efforts.
9. Gives a quick state of the product to the developers after they have done changes in the code.
It is usually unscripted and helps to identify the dependent missing functionality. It is narrow and deep testing that focuses on one or a few areas of functionality. When there are some minor issues within the software and a new build is obtained after fixing the issues then instead of doing complete regression testing sanity is performed on that build. Sanity testing helps to avoid the wastage of time and cost if the build is failed. Sanity testing helps to check that after minor fixes done in a small section of code, the functionality is working as expected & not breaking related functionality .
When we Perform Sanity Testing?
Sanity testing is performed when development team needs to know quick state of the product after they have done changes in the code or there is some controlled code change in a feature to fix any critical issue, and stringent release time-frame does not allow complete regression testing.
Importance of Sanity Testing
1. Sanity testing makes the tester confident about the functionality of an application.
2. Sanity testing assures that the part of the system or methodology works roughly as expected.
3. Using sanity testing the testers makes sure that the basic functionality of an application is working fine and the proposed functionality works roughly as expected.
4. By performing sanity testing on a Mobile Device Testing will be sure that the application will be working fine on other mobile devices having the same operating system.
5. Sanity testing is not documented and thus it saves time and is easy to perform.
6. Sanity testing gives a rough idea of the functionality of the application and the number of uncertainties in the application due to bug fixes.
7. Sanity testing is beneficial when the time for a particular project is limited and tester has already checked the project in detail.
8. Sanity testing does not require many testers and thus saving testing efforts.
9. Gives a quick state of the product to the developers after they have done changes in the code.
