test-fixing
Fix Failing Tests Systematically
When tests fail after refactoring or code changes, this skill groups errors by type and root cause, then fixes each group methodically to get the test suite passing.
Die Skill-ZIP herunterladen
In Claude hochladen
Gehe zu Einstellungen → Fähigkeiten → Skills → Skill hochladen
Einschalten und loslegen
Teste es
Verwendung von "test-fixing". The tests are failing after my recent refactor. I renamed several modules and now have 12 failing tests.
Erwartetes Ergebnis:
Running test suite to identify all failures...
Found 12 failing tests:
- 6 ImportErrors (module renaming impact)
- 4 AttributeErrors (function signature changes)
- 2 AssertionErrors (logic changes)
Prioritizing by impact:
1. ImportErrors (6 tests) - fixing first
2. AttributeErrors (4 tests)
3. AssertionErrors (2 tests)
Starting with ImportError group: analyzing module structure...
Verwendung von "test-fixing". Help me fix the failing tests in the API module. They started failing after I updated the dependencies.
Erwartetes Ergebnis:
Running focused test on API module: pytest tests/api/ -v
Grouping failures by error type:
- 3 ImportError (missing dependency)
- 2 AssertionError (API response format changed)
Following fix order strategy:
1. Fix infrastructure: add missing dependency
2. Fix logic: update assertion for new response format
Verifying each fix with targeted test runs...
Sicherheitsaudit
SicherAll static findings are false positives. The skill is documentation-only (SKILL.md) with no executable code. The detected 'external_commands' are markdown examples of CLI commands, not actual shell executions. The 'weak cryptographic algorithm' finding is a scanner misidentification with no cryptographic code present.
Qualitätsbewertung
Was du bauen kannst
Fix Tests After Refactoring
After renaming modules or functions across a codebase, this skill helps identify all affected test failures, groups them by type, and systematically fixes each group.
Handle CI/CD Test Failures
When CI pipeline fails due to test errors, use this skill to group failures, understand root causes, and fix systematically before retrying the pipeline.
Debug Multiple Test Failures
When running a large test suite reveals many failures, this skill helps prioritize which to fix first based on dependency order and impact.
Probiere diese Prompts
The tests are failing after my recent changes. Please help me fix them using the test-fixing skill. Run the test suite first to see all failures.
I refactored my codebase and now 15 tests are failing. Use smart error grouping to categorize these failures and fix them in the right order. Start by running make test to see all failures.
My CI pipeline failed due to test errors. Use the test-fixing skill to identify the root cause of each failure. Prioritize infrastructure issues like import errors and missing dependencies first.
I have 5 ImportError failures in my auth module tests. Fix these specific failures first, verify they pass, then we will move to other error groups.
Bewährte Verfahren
- Run focused test subsets after each fix to verify the change works before moving to the next group
- Fix infrastructure issues (imports, dependencies, config) before logic bugs for cleaner error states
- Use git diff to understand what changed recently and identify root causes of test failures
- Keep changes minimal and focused - fix one issue at a time rather than bulk changes
Vermeiden
- Fixing all tests at once without running subsets - this makes it hard to identify which fix resolved which error
- Ignoring infrastructure errors and trying to fix logic errors first - import failures will mask real issues
- Making large, sweeping changes instead of targeted fixes - increases risk of introducing new bugs
- Skipping the final full test suite run - may miss regressions introduced during fixing