Sanity_vs_Regression_testing.md

Criteria	Sanity Testing	Regression testing
Goal	The goal of sanity testing is to check that the application is stable enough to proceed with further testing of the entire application.	The goal of regression testing is to ensure that the new code changes does not break the existing functionality of the software.
Scope	The scope of sanity testing is to verify only the specific functionality, verifying the bug fix or configuration or environment related changes.	Regression testing covers overall software or critical features of the software to verify everything is working as expected.
When Performed?	Sanity testing is performed after minor bug fixes, enhancements or before getting into comprehensive testing.	Regression testing is performed after a new feature is added to the software or major rework is done.
Test Cases Used	Basic functional test cases like Login/Logout, navigation, etc. to check that the build is stable after the bug fix or enhancement.	Regression testing considers all the passed and failed test cases to check the overall stability of the software.
Example	For example, there was a bug identified on the login page of the application where on clicking the login button, an error message was thrown, denying user to login. Once this issue is fixed, a sanity check would involve quickly checking that the login functionality is working and user is able to login successfully.	For example, adding new option to sign using Google/Apple ID does not break the existing login functionality using Email ID. Regression Testing will cover checking all the sign-in options to verify that the login works fine.