upgrade junit to jupiter #396
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
|
There is lots and lots of code, but this should be safe. I recommend merging. Why would it be faster? |
|
Mostly parallelism at the method level, rather than class. Most of this is search and replace except for the parameterised tests, but note that none of the implementation classes have changed and the coverage didn't change, so the test suite must be doing the same thing. The main benefit of merging this is being able to write and parallelise parameterised tests easily. |
Smallhi
pushed a commit
to Smallhi/RoaringBitmap
that referenced
this pull request
Jun 14, 2021
upgrade junit to jupiter
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.
upgrades to JUnit 5 ("jupiter") which has some nice features, is faster, and is very stable now