Contributions to JUnit 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.
Official CI build that performs quick checks on submitted pull requests and runs
build matrices for the latest release and early access versions of OpenJDK.
Code Coverage
Code coverage using JaCoCo for the latest build is available on Codecov.
A code coverage report can also be generated locally via the Gradle Wrapper by
executing ./gradlew clean jacocoRootReport. The results will be available
in build/reports/jacoco/jacocoRootReport/html/index.html.
The latest Build Scans are available on develocity.junit.org. Currently,
only core team members can publish Build Scans on that server.
You can, however, publish a Build Scan to scans.gradle.com by
using the --scan parameter explicitly.
The remote Build Cache is enabled by default for everyone so that local builds can reuse
task outputs from previous CI builds.
Building from Source
You need JDK 25 to build JUnit. Gradle toolchains are used to detect and
potentially download additional JDKs for compilation and test execution.
All modules can be built and tested with the Gradle Wrapper using the following command:
./gradlew build
All modules can be installed in a local Maven repository for consumption in other local
projects via the following command:
./gradlew publishToMavenLocal
Dependency Metadata
Consult the Dependency Metadata section of the User Guide for a list of all artifacts
of the JUnit Platform, JUnit Jupiter, and JUnit Vintage.
评论