What is Sanity Testing?
Sanity testing is a targeted, narrow test pass performed after a specific bug fix or change to confirm that the affected functionality works correctly without testing the broader application. It is narrower than smoke testing, which checks that the whole build is usable, and it decides whether a deeper regression run is worth starting.
No account needed · Scored in under a minute against a senior rubric
What does Sanity Testing mean in practice?
Where smoke testing is broad and shallow (does the application start?), sanity testing is narrow and deep (does this specific fix actually work?). Sanity testing is typically unscripted and quick, performed by a QA engineer who understands the area of the change.
The purpose is to verify that it is worth investing time in a full regression run. If a developer fixes a login bug, the sanity test confirms login now works for the affected scenario before the QA team runs the full suite. If the sanity test fails, the build is returned to development immediately.
Sanity testing is especially important in fast-moving teams that ship multiple builds per day. Rather than running the full 4-hour regression suite for every minor patch, a quick 10-minute sanity pass can gate the build efficiently.
Common confusion: sanity testing and smoke testing are often used interchangeably, but they are distinct. Smoke testing covers critical paths across the entire application. Sanity testing covers a specific area after a targeted change.
Why do interviewers ask about Sanity Testing?
Interviewers use sanity testing to test whether you can differentiate between test types. Correctly explaining the distinction from smoke and regression testing demonstrates process maturity and experience with real-world QA workflows.
What does Sanity Testing look like in a real project?
A developer fixes a bug where the "forgot password" email was going to spam due to a misconfigured sender domain. The sanity test verifies that the email now arrives in the inbox, the link is valid, and the password reset completes. This takes 5 minutes and gates the build before regression testing begins.
How should you talk about Sanity Testing in an interview?
Always contrast sanity testing with smoke testing when asked. Smoke = broad, shallow, whole application. Sanity = narrow, deep, specific change. Showing you know the distinction tells interviewers you have done real QA work.
Go Deeper on Sanity Testing
Know the term. These are the courses that turn the concept into something you can demonstrate.
Which terms relate to Sanity Testing?
Explore related glossary terms to deepen your understanding.
Related Resources
Dive deeper with these related interview prep pages.
Free QA career tools, no account needed
Instant and private, everything runs in your browser. Try them before you sign up.
QA Resume Checker
Instant 0-100 score on automation keywords, impact, and ATS formatting.
QA Cover Letter Generator
A tailored 3-paragraph QA cover letter from your resume and a job post.
QA Application Tracker
Drag-and-drop kanban to track every QA application from Applied to Offer.
QA Take-Home Test Generator
A realistic take-home assignment with a scenario, tasks, and a rubric.
QA LinkedIn Headline Generator
A recruiter-searchable headline, About section, and skills list.
QA STAR Story Builder
Structure a QA behavioral answer with the STAR method and instant checks.
QA Bug Report Generator
Build a clean, reproducible bug report for Markdown, Jira, or plain text.
Boundary Value Analysis Generator
Generate boundary value and equivalence partitioning test cases from a range.
QA Metrics Calculator
Calculate DRE, defect leakage, defect density, and pass rate with interpretation.
QA Test Plan Generator
Build a structured test plan (scope, approach, criteria, risks) in Markdown.
QA Salary Calculator
Estimate QA, SDET, and automation tester pay by level, market, and skills.
QA Offer Evaluator
See total comp, a counter range, and a ready-to-send negotiation message.
Ready to Ace Your QA Interview?
Practice explaining sanity testing and other key concepts with our AI interviewer.
Join 500+ QA engineers already practicing with AssertHired.
A test passes locally but fails in CI about one run in five. Walk me through what you check first, and why.
Scored on the same four dimensions as the real thing: Technical accuracy · Coverage · Clarity · Best practices.
Rather skip ahead? Create a free account