gpsaggese/helpers / .claude/skills/testing.reach_coverage
testing.reach_coverage
VerifiedIncrease unit test coverage toward 100 percent for a function or file
Goal
- Given the passed function, file, or files
<FILES>, raise unit test coverage in the test files<TEST_FILES>toward 100 percent, using a plan-then-implement approach
Workflow
Establish Current Coverage
-
Identify the test files for the target, using the rules
- E.g.,
helpers/hllm_cli.py -> helpers/test/test_hllm_cli.py
- E.g.,
-
Print the files to test
Target files: <FILES> Test files: <TEST_FILES> -
Run the command below and record the results:
# Using invoke (preferred): > i run_coverage --suite fast --generate-html-report # Or directly with pytest inside Docker: > pytest --cov=<PKG> --cov-report=term-missing --cov-report=html <TEST_FILE> -
Summarize which lines and branches are not covered
Design a Testing Plan
- Analyze the uncovered code paths and behaviors
- Propose a clear testing plan that:
- Tests functions modularly before testing interactions
- Prioritizes end-to-end and user-visible behavior over incidental implementation details
- Avoids testing assertions, defensive checks, or invalid inputs unless they are critical to correctness
- Explicitly map each uncovered area to one or more proposed tests
Specify Tests Without Implementation
- Define test classes and test method names
- For each proposed test:
- Describe the input data
- Describe the expected output or observable behavior
- Do not write executable test code at this stage
Implement After Approval
- Wait for user confirmation or feedback on the testing plan
- After approval:
- Implement the tests according to the approved plan
- Re-run coverage and verify that coverage for the target function is near 100 percent
- Report final coverage results and remaining gaps, if any
Important Rules
- Do not implement tests before the plan is approved
- Always adhere to the formatting and style guides referenced above
- Focus on meaningful behavior and correctness rather than superficial coverage
- All tests and code must strictly follow:
.claude/skills/coding.rules.mdfor any Python code.claude/skills/testing.rules.mdfor tests
- If any part of the task is unclear or underspecified, stop and ask for clarification before proceeding
Verification
- Confirm coverage for the target function or file is near 100 percent
- Confirm every proposed test was implemented and passes
- Confirm no uncovered critical branch remains unexplained
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: 318k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 318k | 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: 196k | Updated | Claude CodeCodex | Verified | Install |