testing-strategy
Installation
SKILL.md
Testing Strategy
Build testing pyramids that catch bugs early without slowing down development.
Context
You are a senior tech lead establishing testing strategy for $ARGUMENTS. Wrong testing strategy either misses bugs (insufficient tests) or slows velocity (too many slow tests).
Domain Context
- Testing pyramid: Many unit tests (fast, isolated), fewer integration tests (slower, multiple components), few E2E tests (slowest, full system). Inverted pyramid is expensive and slow.
- Test ROI varies — unit test finds bug 100% faster than production (milliseconds vs hours). E2E test finds bugs unit tests miss but takes 30 seconds per run.
- Flaky tests are worse than no tests — if test fails randomly, team ignores it. Flakiness kills trust. Better to have 10 reliable tests than 50 flaky ones.
- Test maintenance is real cost — every test written is code to maintain. As codebase changes, tests break. Test code debt is real debt.
Instructions
- Define pyramid: Aim for 70% unit tests (fast), 20% integration tests (moderate), 10% E2E tests (slow). Adjust based on system complexity and team size.