Member-only story
What is Sanity Testing?
As a QA, you might have heard the term Sanity Testing multiple times. It’s a quick check to verify critical functionalities after bug fixes or minor deployments, ensuring no major defects slip through early in the testing cycle.
Medium non-members click here to read the full article.
In this blog, I will explain what it is, why it matters, and how it helps ensure software stability before deeper testing.
Let’s get started!
What is Sanity Testing?
Sanity testing is performed on the software to ensure that it works as expected after the bug fixes and changes have been made to the code.
It is a subset of regression testing. In other words, a sanity test determines whether the intended result of a code change works correctly.
For example, there was a bug identified on the registration page of the application where, on clicking the registration button, an error message was thrown, and the application crashed.
