Support JUnit5 #395
Merged
Support JUnit5 #395
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
KengoTODA
force-pushed
the
support-junit5
branch
from
4bb64b0
to
b0f120c
Compare
KengoTODA
force-pushed
the
support-junit5
branch
from
b0f120c
to
6c63c6f
Compare
henrik242
approved these changes
Oct 15, 2017
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.
JUnit5 is released recently. It does not support
@Rulenatively, so it is nice to provide JUnit5 extension instead.To provide isolated module for each of JUnit 4 and JUnit 5, I create new module
test-harness-coreto share core logic.Here is example of usage. Currently this module provide no matcher support, because JUnit5 itself does not depend on hamcrest.