Quick Notes117 words
Comprehensive testing strategy — quick notes
Testing strategy — quick notes
| Level | Scope | Runs |
|---|---|---|
| Local | Pre-commit, developer machine | Before push |
| Unit | One component, faked dependencies | Every PR |
| Integration | Components + real dependencies | PR or main |
| Load / performance | Expected and peak traffic | Scheduled / pre-release |
- Cost of a defect: local (minutes) → PR (a build) → production (an incident).
- Push tests as early as they can meaningfully run.
- Load tests need a production-like environment; results are statistical.
Trap: flaky tests train the team to re-run instead of investigate, hiding real regressions. Quarantine or fix — never retry blindly.