HKSM
Smoke Testing
A quick, minimal set of checks run after a build to verify that the product's critical features operate correctly before investing in deeper testing.
Key Points
- Fast, shallow verification focused on essential workflows and services.
- Used to decide if a build is stable enough for further testing or review.
- Typically automated and executed on every build or deployment.
- Not a full regression test; it targets only the most vital functions.
Example
After completing a sprint build, the team runs an automated smoke suite that checks user login, basic navigation, and saving a record. If any check fails, they fix the build before starting detailed regression and exploratory testing.
PMP Example Question
Right after a new build is produced, the team executes a small set of automated checks to confirm login, key navigation, and order submission work before launching full test cycles. What practice is the team performing?
- Smoke testing
- System integration testing
- User acceptance testing
- Exploratory testing
Correct Answer: A — Smoke testing
Explanation: A smoke test is a lightweight set of checks on the most critical functionality to ensure the build is stable enough for deeper testing.
