Skip to content

Sanity testing

Sanity Testing, also known as sanity checks or smoke testing, is a subset of regression testing that focuses on verifying specific functionality or bug fixes in an application. The goal of sanity testing is to ensure that recent changes or additions have not adversely affected the existing functionality of the application. This type of testing is usually performed after receiving a new build to determine if the build is stable enough for further testing. By performing sanity testing, development teams can quickly identify critical issues and ensure that the application is ready for more comprehensive testing.
Related Terms
Regression TestingSmoke TestingFunctional TestingBuild Verification
What is the goal of Sanity Testing?
The goal of Sanity Testing is to verify specific functionality or bug fixes in an application, ensuring that recent changes or additions have not adversely affected the existing functionality of the application.
When is Sanity Testing performed?
Sanity Testing is usually performed after receiving a new build to determine if the build is stable enough for further testing, helping to quickly identify critical issues.
How does Sanity Testing differ from Regression Testing?
Sanity Testing differs from Regression Testing by focusing on specific functionality or bug fixes, while Regression Testing involves verifying that recent code changes have not adversely affected existing functionality.