gpsaggese/helpers / .claude/skills/pytest.fix_local_tests
pytest.fix_local_tests
VerifiedAnalyze and fix failure of local tests
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.1 KB |
SKILL.md
View on GitHub---
description: Analyze and fix failure of local tests
model: haiku
---
# Goal
- Given info about failed tests `<FAILURE_INFO>`, run the tests, find the root
cause, and fix them
# Workflow
## Run Tests
- The input `<FAILURE_INFO>` can be:
- A failing pytest test
- E.g., `dev_scripts_helpers/documentation/test/test_notes_to_pdf.py`
- A repro generated by `pytest_failed_multi_build.py`
- E.g., `tmp.pytest_failed_multi_build.repro.sh`
- Gather information about the failing tests by:
- Reading the code
- Inspecting the content of `<FAILURE_INFO>`
- Running the tests locally, if needed
- E.g.,
```bash
> pytest_log `<FAILURE_INFO>`
> tmp.pytest_failed_multi_build.repro.sh
```
## Analyze Failures
- Read `.claude/skills/pytest.rules.md` to learn how to diagnose issues
- Collect the failing tests from the run
```bash
> i pytest_failed
...
Failed tests: 25/7
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_actions::test1
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_actions::test2
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_edge_cases::test1
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_edge_cases::test2
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_edge_cases::test3
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_edge_cases::test4
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_filters::test1
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_filters::test2
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_filters::test3
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_filters::test4
dev_scripts_helpers/documentation/test/test_notes_to_pdf.py::Test_notes_to_pdf_filters::test5
...
13:07:36 - WARN lib_tasks_pytest.py pytest_failed:1745 To run the failed tests run: tmp.pytest_failed.sh
...
```
- For tests that run Docker / Apple containers, run them with different builds,
per `## Analyze the Effect of Container Builds` in
`.claude/skills/pytest.rules.md`
- Check whether the root cause and the solution are the same for all 3 builds
## Prepare A Plan to Fix Failures
- Prepare a plan following `# Format for Unit Test Fixing Plan` in
`.claude/skills/pytest.rules.md`
- Save it in `plan-pytest.fix_local_tests.md` in the current dir
- Do not print anything on screen
## Implement and Verify the Fix
- If the root cause and the fix are clear, implement the fixes directly
- If the root cause or the fix is unclear, stop and ask the user before
implementing anything
- Verify the fixes as per `# Verification of the Fix` in
`.claude/skills/pytest.rules.md`
# Verification
- [ ] `plan-pytest.fix_local_tests.md` lists a fix for every failing test
- [ ] Every fix follows `# Verification of the Fix` in
`.claude/skills/pytest.rules.md`
- [ ] The failing tests pass locally after the fix
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |