Expand test coverage with edge cases and integration scenarios.
Act as a senior QA engineer designing comprehensive test coverage for [FEATURE] based on requirements: [REQUIREMENTS]. Generate a test matrix including: 1) Happy Path: Five core success scenarios covering primary use cases. 2) Edge Cases: Three boundary conditions (e.g., empty inputs, rate limits). 3) Failure Modes: Two expected failure scenarios with graceful handling. 4) Performance: One load test (specify metrics like RPS or latency). 5) Security: One vulnerability test (e.g., SQLi, XSS). Format each test as a Gherkin scenario with: Given (preconditions), When (actions), Then (assertions), Priority (P0-P2), and Test Type (Unit/Integration/E2E). Use [TEST_DATA] placeholders for dynamic values. The tone must be executable—any engineer should replicate the test verbatim. Highlight flakiness risks (e.g., 'Avoid clock-dependent assertions') and include a 'Test Data Generation' subsection with edge case examples.
When developing new features that need thorough test coverage.