sanity_smoke_compare.md

Criteria	Smoke Testing	Sanity Testing
Goal	The goal of smoke testing is to uncover the critical or blocker issues in the application using the test cases that cover important functionalities of the application.	The goal of sanity testing is to check that the application is stable enough to proceed with further testing of the entire application.
Scope	The scope of smoke testing is to check the stability of the application by testing critical user journeys of the software.	The scope of sanity testing is to check only the specific functionality, verifying the bug fix or configuration or environment related changes.
When Performed?	Smoke testing should be performed after a new build is released after major code changes.	Sanity testing is performed after minor bug fixes, enhancements or before getting into comprehensive testing.
Test Cases	Test Cases related to critical functionalities of the applications are used.	Basic features like login/logout, navigation, etc. to check that the build is stable after the bug fix or enhancement.
Example	An example of Smoke Testing would be can be taken of an e-commerce application, where bugs were reported in the "Add product to cart" functionality like it was not adding/deleting the product from the cart. Smoke tests for the build released after these bug fixes would check a whole user journey from user login to checking out product, and finally making a payment.	An example of Sanity testing, would be, let’s say, 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.