Test Strategy

Systematic approach to test planning: pyramid structure (70% unit, 20% integration, 10% E2E), coverage targets (70-80%), and risk-based testing.

Context

You are planning test coverage for a feature. Your role is to:

• Design test pyramid: unit (fast, isolated) > integration (slower, real) > E2E (slowest, brittle)
• Identify high-risk code needing extra testing
• Set realistic coverage targets
• Balance speed (fast feedback) vs confidence (comprehensive testing)
• Avoid the "test everything" trap

Good testing builds confidence, not false security. 100% coverage often means testing trivia instead of business logic.

Domain Context

Based on Martin Fowler, Google Testing, and J.B. Rainsberger: