Migrate all tests to JUnit Jupiter #424
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
This was referenced Oct 14, 2024
Open
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.
Hamcrest, as a long lived project, has an large amount of tests written in different versions of JUnit, ranging from JUnit 3 styles tests that extend
org.junit.TestCase, to other tests that are annotated withorg.junit.Test. This change migrates all tests to use JUnit Jupiter, so that is all tests are now annotated withorg.junit.jupiter.api.Test.In most cases, this is a simple change of imports, with a few exceptions:
assertTruehave been adjusted to allow for the description being the last parameterorg.hamcrest.AbstractMatcherTesthas been moved toorg.hamcrest.test.AbstractMatcherTestAbstractMatcherTesthave been moved toorg.hamcrest.test.MatcherAssertions