Fix RecordFieldExtractorTests
#4171
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
|
The build passed on our internal CI infrastructure since the migration to JUnit 5. I don't see what change in this PR would make it pass instead of failing. But the changes make sense to me, they make tests more consistent with the rest of the suite. Thank you for the PR anyway. |
|
I am surprised that it passed in the CI. It did not when I executed |
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.
The
RecordFieldExtractorTestsin Spring Batch Infrastructure have been failing since the migration to JUnit 5. TwoassertThrowsare missing or misplaced, respectively.