Create a JUnit3 -> JUnit4 migration tool.#5772
Merged
copybara-service[bot] merged 1 commit intomasterfrom May 4, 2026
Merged
Conversation
It performs fairly well so far. E.g., unknown commit unknown commit PiperOrigin-RevId: 910171949
copybara-service
Bot
force-pushed
the
test_908159560
branch
from
5a46a90 to
13bec96
Compare
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
1 participant
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.
Create a JUnit3 -> JUnit4 migration tool.
It performs fairly well so far. E.g., unknown commit unknown commit