[MINOR] Migrate file status reuse test to JUnit 5 - #3813
Merged
Fokko merged 1 commit intoSep 21, 2026
Merged
Conversation
Fokko
approved these changes
Sep 21, 2026
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.
Rationale for this change
#3674 introduced some test code that is failing the JUnit 5 linter checks due to use of Junit4 helpers like
assertEquals. These checks now fail on the master branch.What changes are included in this PR?
This PR fixes the assertions to use JUnit5 helpers.
Are these changes tested?
Ran spotless locally, everything succeeded. CI checks on this PR should be the authoritative source.
Are there any user-facing changes?
No.