Smoke Testing: Smoke testing is an initial testing done to check if the critical functionalities of the application are working fine. It is a quick and shallow test that aims to identify major issues before proceeding to more comprehensive testing. Smoke testing is usually performed after a new build is released to ensure that the core functionalities of the application are functioning correctly. Smoke testing is also referred to as “Build Verification Testing (BVT)”.
Sanity Testing: Sanity testing, also known as “Quick Test” or “Confidence Test,” is a testing technique used to check if the new changes added to the application are working as expected, without doing an exhaustive regression test. Sanity testing is conducted after a specific change is made to the application, such as a bug fix or a feature enhancement, to ensure that the changes did not cause any unexpected issues in the application.
The main difference between smoke testing and sanity testing is that smoke testing aims to identify showstopper issues in the application before proceeding with in-depth testing, whereas sanity testing aims to verify if specific changes made to the application are functioning as expected without performing a complete regression test. Both smoke testing and sanity testing are important types of testing that help to ensure that the software application is stable and functional.
Types of Smoke Testing:
- Functional Smoke Testing – This type of testing verifies the critical functionalities of the application.
- Integration Smoke Testing – This type of testing verifies if the modules or components of the application are working together as expected.
- Regression Smoke Testing – This type of testing verifies if the new changes made to the application did not affect the existing functionalities of the application.
Types of Sanity Testing:
- Functional Sanity Testing – This type of testing verifies if the new changes made to the application are functioning as expected without affecting the existing functionalities of the application.
- Regression Sanity Testing – This type of testing verifies if the new changes made to the application did not cause any regression issues in the application.