Explore testing strategy options. System context: {{system_context}} Current coverage: {{current_coverage}} Constraints: {{constraints}} ## STRATEGY 1: Heavy Unit Testing - Focus on comprehensive unit tests - Coverage target: 90%+ - Mocking strategy - CI integration approach - Pros: [list] - Cons: [list] - Maintenance burden: [low/medium/high] ## STRATEGY 2: Integration-First - Focus on integration tests - Test environment requirements - External dependency handling - Coverage target - Pros: [list] - Cons: [list] - Maintenance burden: [low/medium/high] ## STRATEGY 3: E2E-Focused - Focus on end-to-end user journeys - Test infrastructure needed - Flakiness mitigation - Coverage of critical paths - Pros: [list] - Cons: [list] - Maintenance burden: [low/medium/high] ## STRATEGY 4: Contract Testing - Focus on API contracts between services - Contract verification approach - Consumer-driven contracts - Provider verification - Pros: [list] - Cons: [list] - Maintenance burden: [low/medium/high] ## RECOMMENDED STRATEGY - Optimal mix of approaches - Test pyramid shape - Investment priorities
Testing Strategy Options
Explore different testing strategies to find the optimal approach.
38 copies0 forks
Share this prompt:
Details
Category
CodingUse Cases
Test strategy developmentQA approach planningTesting investment prioritization
Works Best With
claude-opus-4.5gpt-5.2gemini-2.0-flash
Created Updated Shared