Used JUnit 5 assertion API to keep it consistent with JUnit 5 tests#697
Closed
SampathKumarAmex wants to merge 1 commit into
Closed
Used JUnit 5 assertion API to keep it consistent with JUnit 5 tests#697SampathKumarAmex wants to merge 1 commit into
SampathKumarAmex wants to merge 1 commit into
Conversation
Collaborator
|
LGTM |
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.
Description
Used JUnit 5 assertion API in the test to keep it consistent with JUnit 5
@TestannotationMotivation and Context
Keeping test annotation and assertion API usage consistent in the unit test
How Has This Been Tested?
n/a - Build file change
Screenshots (if appropriate):
n/a
Types of changes
Checklist: