This repository is the home of the next generation of JUnit, JUnit 5.
- General Availability (GA): JUnit 5.2.0 (April 29, 2018).
- Preview (Milestone/Release Candidate): JUnit 5.3.0 RC1 (August 13, 2018).
Contributions to JUnit 5 are both welcomed and appreciated. For specific guidelines
regarding contributions, please see CONTRIBUTING.md in the root directory of the
project. Those willing to use milestone or SNAPSHOT releases are encouraged
to file feature requests and bug reports using the project's
issue tracker. Issues marked with an
up-for-grabs
label are specifically targeted for community contributions.
Ask JUnit 5 related questions on StackOverflow or chat with the team and the community on Gitter.
Code coverage using JaCoCo for the latest build is available on the Jenkins CI server and on Codecov.
A code coverage report can also be generated locally via the Gradle Wrapper by
executing gradlew -PenableJaCoCo clean jacocoRootReport
. The results will be available
in build/reports/jacoco/jacocoRootReport/html/index.html
.
JUnit 5 utilizes Gradle's support for Build Scans. An example build scan for JUnit 5 can be viewed here. Note, however, that the number of listed tests only reflects the Spock tests within the JUnit 5 test suite. To see a full representation of the number of tests executed per project, click on "See console output" on the build scan page.
You need JDK-10 to build JUnit 5.
All modules can be built with the Gradle Wrapper using the following command.
gradlew clean assemble
All modules can be tested with the Gradle Wrapper using the following command.
gradlew clean test
Since Gradle has excellent incremental build support, you can usually omit executing the
clean
task.
All modules can be installed with the Gradle Wrapper in a local Maven repository for consumption in other projects via the following command.
gradlew clean publishToMavenLocal
The following sections list the dependency metadata for the JUnit Platform, JUnit Jupiter, and JUnit Vintage.
See also http://repo1.maven.org/maven2/org/junit/ for releases and https://oss.sonatype.org/content/repositories/snapshots/org/junit/ for snapshots.
- Group ID:
org.junit.platform
- Version:
1.2.0
or1.3.0-RC1
or1.3.0-SNAPSHOT
- Artifact IDs and Automatic-Module-Name:
junit-platform-commons
(org.junit.platform.commons
)junit-platform-console
(org.junit.platform.console
)junit-platform-console-standalone
(N/A)junit-platform-engine
(org.junit.platform.engine
)junit-platform-launcher
(org.junit.platform.launcher
)junit-platform-runner
(org.junit.platform.runner
)junit-platform-suite-api
(org.junit.platform.suite.api
)junit-platform-surefire-provider
(org.junit.platform.surefire.provider
)
- Group ID:
org.junit.jupiter
- Version:
5.2.0
or5.3.0-RC1
or5.3.0-SNAPSHOT
- Artifact IDs and Automatic-Module-Name:
junit-jupiter-api
(org.junit.jupiter.api
)junit-jupiter-engine
(org.junit.jupiter.engine
)junit-jupiter-migrationsupport
(org.junit.jupiter.migrationsupport
)junit-jupiter-params
(org.junit.jupiter.params
)
- Group ID:
org.junit.vintage
- Version:
5.2.0
or5.3.0-RC1
or5.3.0-SNAPSHOT
- Artifact ID and Automatic-Module-Name:
junit-vintage-engine
(org.junit.vintage.engine
)
- Group ID:
org.junit
- Artifact ID
junit-bom
- Version:
5.2.0
or5.3.0-RC1
or5.3.0-SNAPSHOT
All published JAR artifacts contain an Automatic-Module-Name manifest attribute whose value is used as the name of the automatic module defined by that JAR file when it is placed on the module path. The names are listed above in the Dependency Metadata section.
This allows test module authors to require well-known JUnit module names as can be seen in the following example:
open module foo.bar {
requires org.junit.jupiter.api;
requires org.junit.platform.commons;
requires org.opentest4j;
}
The junit-platform-console-standalone
JAR does not provide an automatic module name
as it is not intended to be used as a module.