Repository navigation
[P1] Share auto-patch logic between verify --fix and generation loop #10
Description
Problem
Auto-patching exists only in verify --fix. The generation self-healing loop (#2) needs the same fix-application path. Avoid duplicate logic.
Tasks
- Extract diagnosis→patch application into a reusable function/service (core, not CLI command).
- Call it from both
verify --fixand generator phase 3. - Unit test the shared patcher.
Acceptance
Single code path applies fixes; both entrypoints use it.
Activity
pro-utkarshM commentedon Oct 15, 2026
Done on
master.code2test verify --fixbuilds aTestGeneratorand calls the sameverify_and_fixthat generation uses (code2test/cli/commands/verify.py), so one code path applies every repair.--fixonly rewrites files Code2Test generated and that haven't been edited since.Covered by
tests/test_cli.py:test_verify_fails_after_code_change_and_fix_repairs,test_verify_fix_does_not_overwrite_hand_edited_tests,test_unfixable_tests_are_not_written. Generation-side repair is covered intests/test_pipeline.py.Generated by Claude Code