1523 junit5 upgrade #1533
Merged
1523 junit5 upgrade #1533
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
xael-fry
force-pushed
the
1523_junit5-upgrade
branch
5 times, most recently
from
7ea7306 to
7856c5a
Compare
xael-fry
force-pushed
the
1523_junit5-upgrade
branch
from
7856c5a to
efc1485
Compare
xael-fry
added
feature
improvement
dependencies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Pull Request Checklist
Helpful things
Fixes
Fixes #1523
Purpose
Updating to JUnit 5 would not only enhance our testing capabilities but also align our project with modern Java practices. It would be beneficial to provide training sessions for the team to familiarize them with the new features and best practices in JUnit 5. Screenshots or documentation of JUnit 5 features could be included to illustrate the benefits of the upgrade.