OLD Prototype
The goal of the prototype phase is to come up with some working code that will entice people to give us feedback on the programming model, APIs, and SPIs as described in the sections below. At the current stage, we are NOT COLLECTING FEEDBACK ABOUT THE IMPLEMENTATION, simply because it's in large parts neither polished, nor thoroughly tested, nor stable.
We are also not accepting any pull requests at this time, for the following reasons:
- Focus: The goal of the prototype is to get feedback on the API and programming model. Focusing on code style, formatting, and other details will distract the community's (and our) attention. A lot of the code in the prototype will potentially be rewritten anyway.
- Legal reasons: Any contributor will have to sign a contributor's agreement as outlined in the CONTRIBUTING guidelines. The exact details have not been figured out yet, but we will contact you before accepting your first pull request.
If you want to provide input in the interim, please use the project's issue tracker or send us comments via Twitter.
JUnit 5 only supports Java 8 and above. However, you can still test classes compiled with lower versions.
Snapshot artifacts are deployed to Sonatype's snapshots repository.
-
Group ID:
org.junit.prototype -
Version:
5.0.0-SNAPSHOT -
Artifact IDs:
junit-commonsjunit-consolejunit-engine-apijunit-gradlejunit-launcherjunit4-enginejunit4-launcher-runnerjunit5-apijunit5-engine-
open-test-alliance(Version1.0.0-SNAPSHOT) surefire-junit5
See also: https://oss.sonatype.org/content/repositories/snapshots/org/junit/prototype/
You can find a collection of sample projects based on the JUnit 5 prototype in the junit5-samples repository. You'll find the respective build.gradle
and pom.xml in the projects below:
- For Gradle, check out the junit5-gradle-consumer project.
- For Maven, check out the junit5-maven-consumer project.
How to write test cases in JUnit 5?
How to run existing JUnit 4 tests with JUnit5 and migrate from JUnit 4 to JUnit 5?
The JUnit 5 Launcher API page is primarily targeted at IDE and build tool providers.
There is also a short paragraph on how to plug other test engines into the launcher.
Based on discussions with IDE and build tool developers from Eclipse, Gradle, and IntelliJ, the JUnit Lambda team has launched an initiative called the Open Test Alliance for the JVM, an open source project to provide a minimal common foundation for testing libraries on the JVM. The primary goal of the project is to enable testing frameworks like JUnit, TestNG, Spock, etc. and third-party assertion libraries like Hamcrest, AssertJ, etc. to use a common set of exceptions that IDEs and build tools can support in a consistent manner across all testing scenarios -- for example, for consistent reporting and test execution visualization.
User Guide | Javadoc | Issues