What is Sanity Testing?
Sanity testing is a crucial part of the software testing process, specifically within the realm of manual testing. It is performed to verify that a particular function or bug fix works as intended after changes have been made to the software. This type of testing is not exhaustive but provides a quick evaluation of the software's behavior.
Purpose of Sanity Testing
Sanity testing aims to ensure that the changes in the code do not adversely affect the existing functionalities. It is typically conducted after receiving a software build, focusing on specific functionalities. This helps in determining whether the build is stable enough to proceed with more rigorous testing.
Process of Sanity Testing
The process begins with understanding the modifications made in the software. Test cases are then selected to validate those changes. Testers execute these cases manually to confirm that the new features function correctly and that existing functionalities remain unaffected. If the sanity test fails, the build is rejected, preventing further testing on unstable software.
Difference Between Sanity Testing and Smoke Testing
While both sanity and smoke testing are both types of regression testing, they serve different purposes. Smoke testing checks whether the basic functionalities of the application work correctly, whereas sanity testing focuses more on validating specific functionalities after changes.
In summary, sanity testing is an essential practice within manual testing that ensures new changes work as intended before extensive testing is performed. It helps maintain software quality and stability, which are critical in the software development lifecycle.