Smoke Test
A Smoke Test is a small, fast check set. It shows whether a build can receive deeper tests or use.
Another example
After deployment, automation opens the home page and signs in with a test account. It reads one API reply and submits a harmless transaction.
Main parts
- 01Code or behavior under test
- 02Observable evidence
- 03Coverage, failure, and recovery
Use it when
Run it after packaging or deployment. Stop clearly broken versions before long tests or real traffic.
Do not use it when
Do not call a full regression suite a smoke test. A pass does not prove edge cases.
Name used in code
critical-path probes after build/deploy Before you ship
Check the environment and prepared test data (fixture). Define a result you can observe, failure and edge cases, isolation, stable inputs, useful error details, and cleanup. Set a time budget, owner, and flaky-test rule.
Outcome: Use Smoke Test to gather repeatable evidence about this behavior or quality risk. User context: After deployment, automation opens the home page and signs in with a test account. It reads one API reply and submits a harmless transaction. Validation approach: Smoke Test. Why it fits: Run it after packaging or deployment. Stop clearly broken versions before long tests or real traffic. Do not use it when: Do not call a full regression suite a smoke test. A pass does not prove edge cases. Test requirements: Name the system and test environment. Define prepared test data, other inputs, and the result you can observe. Include failure and edge cases, allowed error, isolation, and cleanup. Test operations: Make failures easy to diagnose. Control random or changing inputs. Name an owner. Keep the test fast and simple enough for its release gate. Acceptance criteria: The test fails for the known bug and passes after the fix. It repeats in the target environment, gives useful evidence, and does not expose or change unrelated data. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Release gate, environment, prepared test data, allowed error, time budget, owner, and flaky-test rule.
Check this request
Review the current use of Smoke Test. Definition: A Smoke Test is a small, fast check set. It shows whether a build can receive deeper tests or use. Release checks: Check the environment and prepared test data (fixture). Define a result you can observe, failure and edge cases, isolation, stable inputs, useful error details, and cleanup. Set a time budget, owner, and flaky-test rule. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.