Require migration of ALL tests in excavator instructions#349
Merged
Conversation
The Claude agent was only migrating a subset of tests (e.g., 5 out of 60+) as "representative samples". This adds an explicit instruction that every single test must be migrated. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
crogoz
approved these changes
Jan 22, 2026
|
Released 0.50.0 |
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
2 participants
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.
Before this PR
The excavator JUnit migration instructions didn't explicitly require migrating all tests. This led to Claude deciding to only migrate a "representative sample" of tests (e.g., 5 out of 60+).
After this PR
Added an explicit instruction that every single test method in the original Groovy file must have a corresponding test method in the new Java file. No skipping tests or only migrating "representative samples".
Possible downsides?
Testing
N/A - documentation change