Make sure we use JUnit 5 assertions #2419
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
We had a mix of Junit4/5 assertions. This commit switches to the JUnit 5 jupiter assertions. Also uses specific asserts for nulls and instance checks. And removes public from test classes/methods which were touched
mjperry91
approved these changes
May 21, 2024
sdelamo
approved these changes
May 21, 2024
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.
We had a mix of Junit4/5 assertions.
This commit switches to the JUnit 5 jupiter assertions. Also uses specific asserts for nulls and instance checks. And removes public from test classes/methods which were touched
Closes #2417