Wouldn't it be great to have one test launcher to rule them all? One API that tools need to support and that other test frameworks could implement, so that neither need to know about the other? JUnit5's launching API has that promise.
All it needs is support from the JVM community to provide:
- Launchers to execute JUnit from new (and the same old) places
- TestEngines to support new (and the same old) testing frameworks
Jupiter's main goal is to help provide launchers and engines to extend the support of JUnit5 to new places.
- clojure.test through
org.ajoberstar.jupiter:jupiter-engine-clojure.test
- Gradle 3 through
org.ajoberstar.jupiter:jupiter-launcher-gradle
NOTE: All jupiter modules require Java 8 (or higher).
Please use the repo's issues for all questions, bug reports, and feature requests.
Contributions are very welcome and are accepted through pull requests.
Smaller changes can come directly as a PR, but larger or more complex ones should be discussed in an issue first to flesh out the approach.
If you're interested in implementing a feature on the issues backlog, add a comment to make sure it's not already in progress and for any needed discussion.
Thanks to the JUnit5 team for putting together a great new API!