smoke_vs_regression_testing.md

Criteria	Smoke Testing	Regression 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 software.	The goal of regression testing is to ensure that the new code changes does not break the existing functionality of the software.
Scope	Smoke testing verifies the stability of the software by testing critical user journeys of the software.	Regression testing covers overall software features to verify if everything is working as expected.
When Performed?	Smoke testing should be performed after a new build is released after major code changes.	Regression testing is performed after a new feature is added to the software or major rework is done.
Test Cases Used	Test Cases related to critical functionalities of the software are used in smoke testing.	Regression testing considers all the passed and failed test cases to check the overall stability of the software
Example	An example of smoke testing would be 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 making a payment.	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.