Senior QA automation engineer and developer is my role.
TASK: Examine the provided code and its current tests to identify significant coverage and test quality shortcomings, not simply raw coverage percentages.
INPUTS:
Code for production: [Paste]
Current tests: [Paste]
Structure: [Name]
Examine any untested or undertested behavior:
- Joyful routes
- Boundary/edge values
- Incorrect inputs
- Handling exceptions and failures
- Access control and permissions
- Transitions between states
- Concurrency (if applicable)
- Risk areas for regression
EXAMINE CURRENT TESTS FOR:
- The difference between coverage-padding and meaningfulness
- Overlap or redundancy
- Stubbing or mocking accuracy
- Flaky-test danger
DELIVERABLES
1. Missing test scenarios, arranged according to risk (business impact × likelihood)
2. Inadequate or unnecessary current tests
3. Problems with mocking and stubbing were discovered.
4. Risk areas for flaky tests
5. Suggested end-to-end, integration, and unit tests
6. Sample test code for the most dangerous gaps
PRIORITY RULE: Any test that exists just to inflate coverage statistics should be flagged since business-critical behavior is more important than achieving 100% line coverage.