ai.testers:testersai-junit5
The easiest way to AI-upgrade your existing JUnit 5 suite. You already have the tests — this adds AI Checks at the moments that matter, without replacing your framework, runner, or CI pipeline.
analyze_* call, or define your own.@ExtendWith(TestersAIExtension.class) injects a TestersAIFacade into tests.
# Download testersai-java-junit5-0.1.0.tar.gz from the Downloads page, then:
tar -xzf testersai-java-junit5-0.1.0.tar.gz
cd testersai-java-junit5-0.1.0
mvn -f core/pom.xml install
# ...then reference the junit5_testersai module from your project
A complete, runnable Java + JUnit 5 example.
@ExtendWith(TestersAIExtension.class)
class CheckoutTest {
@Test
void checkout(TestersAIFacade ta) throws Exception {
// ...your Selenium / Playwright code...
ta.screenshot(Files.readAllBytes(Paths.get("cart.png")),
Map.of("stage", "cart"));
ta.screenshot(Files.readAllBytes(Paths.get("success.png")),
Map.of("stage", "success"));
}
}
JUnit 5 ExtensionContext.publishReportEntry() — shows up in standard JUnit reports.
If the AI call fails — rate limit, hang, firewall, no network — the SDK gives up
fast and returns a skipped result. Your JUnit 5 test is never blocked.
Rule of thumb: wherever a human reviewer would pause to look during a manual run. These recommendations are tuned for JUnit 5 — pick the ones that fit your suite.
The page just re-rendered. Ask "does this look right?" before any interaction.
Login, add-to-cart, toggle, submit. The UI just reflected a new state — where regressions hide.
You were about to check one thing. Ask the AI about everything else for free.
API returned, spinner gone, toast shown. Catch broken empty-states and stale data.
A single console + network check at the end of every test catches issues your assertions ignored.
Mobile vs. desktop, light vs. dark, locale change. One call per viewport.
ExtensionContext.publishReportEntry() — shows up in standard JUnit reports.Or grab the monolith ZIP (all languages, all adapters).