Migrate to JUnit 5 - avoid using TestCase#11547
Merged
slawekjaranowski merged 4 commits intoapache:maven-3.9.xfrom Dec 21, 2025
Merged
Migrate to JUnit 5 - avoid using TestCase#11547slawekjaranowski merged 4 commits intoapache:maven-3.9.xfrom
slawekjaranowski merged 4 commits intoapache:maven-3.9.xfrom
Conversation
elharo
approved these changes
Dec 13, 2025
cstamas
approved these changes
Dec 13, 2025
265f470 to
e65ec60
Compare
slachiewicz
approved these changes
Dec 15, 2025
Only simply migration to remove usage of JUnit 3 - TestCase More improvements to tests can be done in the future.
42516e7 to
1cbe627
Compare
Member
Author
|
done - all tests migrated |
36 tasks
slachiewicz
approved these changes
Dec 20, 2025
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
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.
Only simply migration to remove usage of JUnit 3 - TestCase
More improvements to tests can be done in the future.
Following this checklist to help us incorporate your
contribution quickly and easily:
Note that commits might be squashed by a maintainer on merge.
This may not always be possible but is a best-practice.
mvn verifyto make sure basic checks pass.A more thorough check will be performed on your pull request automatically.
If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.