Repository navigation
Support integration test repair and coverage - #28
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Integration candidates previously fell back to source-inserted unit tests during repair and per-candidate coverage, losing their import context and sometimes running duplicate tests.
Add
fix --integrationand keep generation, repair, and coverage in integration targets. Repair imports and helpers per candidate, preserve temporary inputs, and reject mismatched cache modes. Update usage documentation.Validation: workspace tests, the minimal offline pipeline, task/concurrency regression, and all 11 coverage compatibility cases pass. New cases cover imports, helpers, sibling isolation, cached repair, mode mismatch, and failure cleanup. No external model calls.