Resources
Smoke Testing vs Sanity Testing
Smoke testing vs sanity testing without the syllabus fight: a build-level ‘does it start’ check versus a focused check after a change — and how both sit in a real QA process.
Smoke testing vs sanity testing is a naming argument that wastes standups. The useful distinction is scope and trigger, not which ISTQB paragraph you prefer.
We use the words this way on engagements. If your team already swapped the labels, keep your labels and keep the two jobs. Do not rename a 400-case suite “smoke” so it sounds fast.
Smoke testing
A smoke is a short, shallow pass on a new build: does it install, start, sign in, and reach the one or two journeys that mean “this build is not dead”?
- Trigger: a new build lands
- Goal: reject a broken build before anyone spends a day on it
- Size: minutes, not a release
- Owner: often CI plus a human glance
If smoke is red, stop. Do not “also run regression to be sure.”
Sanity testing
A sanity check is a focused pass after a specific change: the fix, the flag, the one flow you touched — plus the nearest neighbour that usually breaks.
- Trigger: a fix or a narrow change is claimed done
- Goal: is this change safe enough to continue?
- Size: the change, not the product
- Owner: the tester (or developer) closest to the ticket
Sanity is not a synonym for “quick regression of everything we like.” That is a short regression pass. Name it that.
How they differ from the rest
| Check | Job |
|---|---|
| Smoke | Is this build alive? |
| Sanity | Is this change roughly right? |
| Regression | Did we break something we already knew worked? |
| Functional | Does the scoped behaviour match the spec? |
| Exploratory | What did the cases miss? |
Smoke and sanity sit at the front of the QA process. They do not replace a plan.
A practical default
- Smoke on every build you might test (automate the dead-build checks).
- Sanity on the ticket that just landed.
- Regression on the agreed list before you call the release done.
- Do not put 80 UI specs in the smoke job. That is an ice-cream cone — see the test pyramid.
FAQs
Is sanity testing a subset of regression?
Often, in practice. The word is still useful if it means “narrow, change-triggered.” If it means “whatever we have time for,” drop it.
Should smoke be automated?
The “does it start / sign in” part, yes, when the product is stable enough. A human still looks at a new visual or a new environment.
How do we start?
Book a QA consultation. Bring your CI job names and what you run on a hotfix. We will say which job is lying about its title.
Talk to our QA team
Want this applied to your next release?
We write and maintain these artefacts on live products — then execute the cases, not only the documents.