junit-team
junit-framework
Java

✅ The programmer-friendly testing framework for Java and the JVM

Last updated Jul 6, 2026
7.0k
Stars
1.7k
Forks
117
Issues
+11
Stars/day
Attention Score
98
Language breakdown
Java 98.4%
Kotlin 1.5%
Groovy 0.2%
Files click to expand
README

JUnit

This repository is the home of JUnit Platform, Jupiter, and Vintage.

Sponsors

Support JUnit

Latest Releases

  • General Availability (GA): JUnit 6.1.1 (June 28, 2026)
  • Preview (Milestone/Release Candidate): N/A

Documentation

  • [User Guide]
  • [Javadoc]
  • [Release Notes]
  • [Examples]

Contributing

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.

Getting Help

Ask JUnit-related questions on [StackOverflow] or use the Q&A category on [GitHub Discussions].

Continuous Integration Builds

CI Cross-Version

Official CI build server used to perform quick checks on submitted pull requests and for build matrices including the latest released OpenJDK and early access builds of the next 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.

Develocity

Revved up by Develocity

JUnit utilizes Develocity for Build Scans, Build Cache, and Predictive Test Selection.

The latest Build Scans are available on ge.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

JUnit Jupiter version JUnit Vintage version JUnit Platform version

Consult the [Dependency Metadata] section of the [User Guide] for a list of all artifacts of the JUnit Platform, JUnit Jupiter, and JUnit Vintage.

[Codecov]: https://codecov.io/gh/junit-team/junit-framework [CONTRIBUTING.md]: https://github.com/junit-team/junit-framework/blob/HEAD/CONTRIBUTING.md [Dependency Metadata]: https://docs.junit.org/current/appendix.html#dependency-metadata [GitHub Discussions]: https://github.com/junit-team/junit-framework/discussions/categories/q-a [Gradle toolchains]: https://docs.gradle.org/current/userguide/toolchains.html [Gradle Wrapper]: https://docs.gradle.org/current/userguide/gradlewrapper.html#sec:usingwrapper [JaCoCo]: https://www.eclemma.org/jacoco/ [Javadoc]: https://api.junit.org [JDK 25]: https://javaalmanac.io/jdk/25/ [Release Notes]: https://docs.junit.org/current/release-notes.html [Examples]: https://github.com/junit-team/junit-examples [StackOverflow]: https://stackoverflow.com/questions/tagged/junit5 [User Guide]: https://docs.junit.org

© 2026 GitRepoTrend · junit-team/junit-framework · Updated daily from GitHub