Lets learn what sanity testing is. The meaning of the word Sanity is the state of being healthy. That means checking whether a particular thing is healthy in a given condition.
It is a quick and narrow test, not a detailed full test.
Simple Definition
It is a type of software testing done to check whether a specific functionality or bug fix is working correctly after small changes in the application.
Example
Suppose developers fixed the Mailbox login button issue.
As a tester, you will:
- Open the application
- Enter username/password
- Click login
- Verify login works properly
You mainly focus on:
- The changed feature
- Related impacted areas
You do NOT test the entire application.
Characteristics of Sanity Testing
- Narrow and focused
- Usually done after bug fixes or minor code changes
- Helps decide whether deeper testing should continue
- Mostly manual testing
- Saves testing time
When is Sanity Testing Performed?
- After receiving a new build with minor changes
- After bug fixes
- Before performing detailed regression testing
Difference Between Sanity and Smoke Testing
| Smoke Testing | Sanity Testing |
|---|---|
| Checks the basic functionality of the whole application | Checks specific functionality |
| Broad and shallow | Narrow and deep |
| Done on every new build | Done after minor changes/bug fixes |
| Ensures the build is stable | Ensures bug fix/change works correctly |
Important Point to Remember
- Smoke Testing = “Can we test?”
- Sanity Testing = “Does the changed feature work correctly?”