Skip to content
Automatically administer lifecycle of JUnit 5 tests using recheck.
Java Shell
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Build Status Latest recheck-junit-jupiter-extension on Maven Central license PRs welcome code with hearth by retest

JUnit Extension for recheck. Automatic set up and tear down of tests using recheck.


  • Calls startTest on all RecheckLifecycle objects before each test.
  • Calls capTest on all RecheckLifecycle objects after each test.
  • Calls cap on all RecheckLifecycle objects after all tests.


The extension automatically calls startTest, capTest and cap. So it is no longer required to call those methods manually. This reduces boilerplate code and ensures the lifecycle within a test using recheck.

Build tools

You can add recheck-junit-jupiter-extension as an external dependency to your project. It is available via the release-page which allows you to include it into your favorite build tool or via Maven central: Latest recheck-junit-jupiter-extension on Maven Central




compile 'de.retest:recheck-junit-jupiter-extension:${LATEST_VERSION_FROM_ABOVE_LINK}'


The recheck JUnit extension uses JUnit's extension mechanism. It can be used as a declarative extension by adding @ExtendWith(RecheckExtension.class) to your test class or globally/automatically by adding a /META-INF/services/org.junit.jupiter.api.extension.Extension file to your project with de.retest.recheck.junit.jupiter.RecheckExtension as its sole contents and setting the junit.jupiter.extensions.autodetection.enabled=true parameter e.g. in your pom.xml or as a JVM system property.


Requires at least JUnit Jupiter. For JUnit 4 support look at recheck extension for JUnit 4.


This project is licensed under the AGPL license.

You can’t perform that action at this time.