Smoke vs Sanity vs Regression vs Retesting

Overview

This guide outlines four core testing objectives: smoke testing, sanity testing, regression testing, and retesting. It clarifies the scope, triggers, and expectations for each approach using practical examples, such as an e-commerce coupon fix and shopping application workflows. The material emphasizes that these categories represent distinct testing purposes rather than rigid project phases executed in a mandatory sequence. Additionally, the notes provide interview guidance, common traps, and post-testing evaluation strategies. Topics detail how to select regression tests based on impact analysis, how to record evidence during defect retesting, and how to handle scenarios where smoke tests either pass or encounter blockers.

Table of contents

1. Stop Mixing Up the Goal
2. Four Questions, Four Testing Goals
3. Smoke Testing: Build Readiness
4. Sanity Testing: Focus on the Change
5. Regression: Protect Existing Behavior
6. Retesting: Confirm the Fix
7. One Coupon Fix, Four Perspectives
8. Smoke Passed. Can We Release?
9. Retest Passed. What About Regression?
10. Smoke Failed. Must All Testing Stop?

Selected preview

A fast, broad check of critical functionality helps decide whether a build is usable enough for the next testing stage. A pass gives initial confidence, not release approval.

Extract from the PDF pages of this resource.

Who this resource is for

• QA Engineers
• Software Testers

Format and what you get

• A downloadable PDF you can read on phone or laptop.
• Included in the QA Notes Vault: one payment unlocks every note in the Vault, with lifetime access to it.
• Download after signing in with the account that paid. Refunds follow our refund policy.

Free learning on this topic

• Manual testing interview questions
• Smoke, sanity and regression testing
• Refund policy