SoftwareTestPilot
Glossary

Smoke vs Sanity Testing — The Clear Difference

Both are quick checks that run before deeper testing. Smoke tests verify the build is stable enough to test. Sanity tests verify a specific change works as expected.

Last updated: June 1970

Smoke vs Sanity

AspectSmokeSanity
GoalBuild stabilityVerify a specific change/bugfix
ScopeBroad, shallowNarrow, focused
WhenAfter every new buildAfter hotfix / minor change
Documented?Usually scriptedOften unscripted
OwnerQA + DevOpsQA

Example

Smoke: 'Can a user log in, see the dashboard, and check out a sample item?' Sanity: 'The hotfix changed the tax calculation for EU orders — does it apply correctly and not break US orders?'

Frequently asked questions

Related reads

Land your next QA role faster

Free AI interview practice, resume ATS review, and a live QA jobs radar.