Test Strategy
Test Strategy vs Test Plan
- Strategy: Organization-level, long-term approach
- Plan: Project-level, specific details
Test Strategy Components
1. Scope
- What to test / not test
- In-scope: functional, regression, performance
- Out-of-scope: with justification
2. Test Levels
/ E2E Tests \ (5%)
/ Integration \ (15%)
/ Unit Tests \ (80%)
3. Test Types
| Type | When | Who |
|---|
| Unit | Every commit | Developers |
| Integration | Every PR | Dev + QA |
| E2E | Daily/Nightly | QA |
| Performance | Pre-release | QA + DevOps |
| Security | Monthly | Security team |
| Exploratory | Every sprint | QA |
4. Environment Strategy
- Dev: Developer testing
- QA: Dedicated test environment
- Staging: Mirror of production
- Production: Smoke tests post-deploy
5. Test Data Strategy
- Synthetic data for most tests
- Anonymized production data for realistic scenarios
- Data refresh schedule
- Test data management tools
6. Defect Management
- Severity/Priority matrix
- SLA for fix times
- Triage process
- Release criteria (zero P1/P2)