test-fixing

Topics in the source

• Test Fixing
• When to Use
• Systematic Approach
• 1. Initial Test Run
• 2. Smart Error Grouping
• 3. Systematic Fixing Process
• 4. Fix Order Strategy
• 5. Final Verification

Systematically identify and fix all failing tests using smart grouping strategies. Explicitly asks to fix tests ("fix these tests", "make tests pass") Reports test failures ("tests are failing", "test suite is broken") Completes implementation and wants tests passing Mentions CI/CD failures due to tests Run make test to identify all failing tests. Analyze output for: Total number of failures Error types and patterns Affected modules/files Group similar failures by: Error type: ImportError, AttributeError, AssertionError, etc. Module/file: Same file causing multiple test failure Root cause: Missing dependencies, API changes, refactoring impacts Prioritize groups by: Number of affected tests (highest impact first) Dependency order (fix infrastructure before functionality) For each group (starting with highest impact): 1. Identify root cause Read relevant code Check recent changes with git diff Understand the error pattern 2. Implement fix Use Edit tool for code changes Follow project conventions (see CLAUDE.md) Make minimal, focused changes 3. Verify fix Run subset of tests for this group Use pytest markers or file patterns: Ensure group passes before moving on 4. Move to next group

This is an excerpt. Refer to the complete source and its current requirements.