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.
Gradle build script has been updated to support JUnit 5 APIs in tests. Logging and reporting of test results has been added.
Supports existing JUnit 4 tests as is, with no changes
JUnit 5 has nicer APIs for writing tests than JUnit 4
Stable API (5.0.0 was release four years ago)
Already supported by all major Java IDEs
With this PR merged, running:
will 1) produce human readable test results in the console and 2) produce nice HTML output in
./build/reports/tests/test/index.html
For vast majority of JUnit 4 tests, the migration is just replacing old imports with new ones. And for most of those it's just replacement of
import static org.junit.Assert.*
withimport static org.junit.jupiter.api.Assertions.*
.