Test Fixing

1---
2name: test-fixing
3description: Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.
4---
5 
6# Test Fixing
7 
8Systematically identify and fix all failing tests using smart grouping strategies.
9 
10## When to Use
11 
12- Explicitly asks to fix tests ("fix these tests", "make tests pass")
13- Reports test failures ("tests are failing", "test suite is broken")
14- Completes implementation and wants tests passing
15- Mentions CI/CD failures due to tests
16 
17## Systematic Approach
18 
19### 1. Initial Test Run
20 
21Run `make test` to identify all failing tests.
22 
23Analyze output for:
24 
25- Total number of failures
26- Error types and patterns
27- Affected modules/files
28 
29### 2. Smart Error Grouping
30 
31Group similar failures by:
32 
33- **Error type**: ImportError, AttributeError, AssertionError, etc.
34- **Module/file**: Same file causing multiple test failure
35- **Root cause**: Missing dependencies, API changes, refactoring impacts
36 
37Prioritize groups by:
38 
39- Number of affected tests (highest impact first)
40- Dependency order (fix infrastructure before functionality)
41 
42### 3. Systematic Fixing Process
43 
44For each group (starting with highest impact):
45 
461. **Identify root cause**
47 
48   - Read relevant code
49   - Check recent changes with `git diff`
50   - Understand the error pattern
51 
522. **Implement fix**
53 
54   - Use Edit tool for code changes
55   - Follow project conventions (see CLAUDE.md)
56   - Make minimal, focused changes
57 
583. **Verify fix**
59 
60   - Run subset of tests for this group
61   - Use pytest markers or file patterns:
62     ```bash
63     uv run pytest tests/path/to/test_file.py -v
64     uv run pytest -k "pattern" -v
65     ```
66   - Ensure group passes before moving on
67 
684. **Move to next group**
69 
70### 4. Fix Order Strategy
71 
72**Infrastructure first:**
73 
74- Import errors
75- Missing dependencies
76- Configuration issues
77 
78**Then API changes:**
79 
80- Function signature changes
81- Module reorganization
82- Renamed variables/functions
83 
84**Finally, logic issues:**
85 
86- Assertion failures
87- Business logic bugs
88- Edge case handling
89 
90### 5. Final Verification
91 
92After all groups fixed:
93 
94- Run complete test suite: `make test`
95- Verify no regressions
96- Check test coverage remains intact
97 
98## Best Practices
99 
100- Fix one group at a time
101- Run focused tests after each fix
102- Use `git diff` to understand recent changes
103- Look for patterns in failures
104- Don't move to next group until current passes
105- Keep changes minimal and focused
106 
107## Example Workflow
108 
109User: "The tests are failing after my refactor"
110 
1111. Run `make test` → 15 failures identified
1122. Group errors:
113   - 8 ImportErrors (module renamed)
114   - 5 AttributeErrors (function signature changed)
115   - 2 AssertionErrors (logic bugs)
1163. Fix ImportErrors first → Run subset → Verify
1174. Fix AttributeErrors → Run subset → Verify
1185. Fix AssertionErrors → Run subset → Verify
1196. Run full suite → All pass ✓
120