Test Type Definitions
Smoke test
Quick verify build doesn't catch fire. Run after every deploy.
- 5-15 phút duration.
- Cover top 10-20 critical path.
- Run automation, manual fallback.
Sanity test
Quick verify specific functionality work as expected after change.
- 15-30 phút.
- Focus on affected area only.
- Like smoke but more targeted.
Regression test
Verify existing functionality still work after change.
- Hours to days.
- Cover all features.
- Mostly automated.
Confirmation test (re-test)
Verify a specific bug fix actually fixed.
- Single test case.
- Run after dev mark "fixed".
- If pass → close bug.
Comparison table
| Type | Scope | Duration | When |
|---|
| Smoke | Broad shallow | 5-15 min | Every deploy |
| Sanity | Narrow shallow | 15-30 min | Hotfix area |
| Regression | Broad deep | Hours | Each release |
| Confirmation | Single bug | Minutes | Each fix |
Other types
- Exploratory — unscripted, charter-based.
- Acceptance — UAT, user/client side.
- Alpha — internal user test.
- Beta — external limited user test.
- Compatibility — cross-platform, cross-browser.
VN context
Common Vietnamese term confuse:
- "Kiểm thử khói" = smoke.
- "Kiểm thử hồi quy" = regression.
- "Kiểm thử chấp nhận" = acceptance.
Standardize team vocabulary onboarding day 1.
QA strategy
- Smoke + Sanity: automated, fast pipeline.
- Regression: weekly + pre-release.
- Confirmation: as needed.
- Exploratory: scheduled bi-weekly.