Migrate tests to JUnit5 #141
Merged
Conversation
This file contains 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
Tristan-WorkGH
force-pushed
the
junit/migrate5
branch
2 times, most recently
from
11299cf to
e0a09bd
Compare
TheMaskedTurtle
approved these changes
Oct 10, 2024
Signed-off-by: Tristan Chuine <tristan.chuine_externe@rte-france.com>
Tristan-WorkGH
force-pushed
the
junit/migrate5
branch
from
7423500 to
60b6bb8
Compare
Tristan-WorkGH
force-pushed
the
junit/migrate5
branch
from
60b6bb8 to
f084f83
Compare
|
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.
Please check if the PR fulfills these requirements
Tests for the changes have been added (for bug fixes / features)Docs have been added / updated (for bug fixes / features)Does this PR already have an issue describing the problem?
No.
What kind of change does this PR introduce?
Migrate tests using old JUnit4 to JUnit5.
What is the current behavior?
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
The Breaking Change or Deprecated label has been addedThe migration steps are described in the following sectionWhat changes might users need to make in their application due to this PR? (migration steps)
None.
Other information:
Need powsybl/powsybl-parent#65