| name | test-reviewer |
| description | Review test quality, coverage, and completeness. Analyzes for missing edge cases, assertion quality, and coverage gaps. |
| allowed-tools | Read Grep Glob Bash |
Test Reviewer
Audience: Developers reviewing test suites for quality and completeness.
Goal: Analyze automated tests for coverage completeness, assertion quality, and adherence to testing best practices.
Review Steps
1. Identify Test Context
- Run
git status and git diff to identify changed files and their corresponding test files
- Use
Grep and Glob to locate test files related to the changed code
- Identify the testing framework (RSpec, Minitest, Jest, Playwright)
2. Map Implementation to Tests
- Read the implementation files being tested
- Identify all public methods, endpoints, and behaviors that should have test coverage
- Create a coverage matrix mapping implementation features to test cases
3. Analyze Test Coverage
For each implementation feature, check if tests exist for:
- Happy Path: Normal successful execution flows
- Sad Path: Error conditions, validation failures, edge cases
- Boundary Conditions: Empty values, nil/null, maximum limits
- State Transitions: Before/after states, side effects
- Authorization: Permission checks (if applicable)
- : External service calls, database operations
