<img src="./Logo.svg" alt="Kensa Logo" style="width: 40px; vertical-align: middle;"/> Kensa

Kensa is a BDD testing framework for Kotlin and Java. Write Given-When-Then tests directly in code — no Gherkin files, no step definitions. Kensa parses your test source at runtime to produce rich HTML reports and sequence diagrams.

Check out the documentation for quickstarts, API reference, and examples.

| Write this… | …get this | |---|---| | | |

Features

• Code-first BDD — Given-When-Then structure in plain Kotlin/Java; no external DSL files
• HTML reports — generated directly from test source, always in sync with the code
• Sequence diagrams — visualise interactions between actors captured during test execution
• Framework support — JUnit 5, Kotest, TestNG
• Assertion libraries — Kotest, AssertJ, Hamcrest, HamKrest

Getting Started

Add the dependency for your test framework:

// build.gradle.kts
dependencies {
    testImplementation("dev.kensa:kensa-junit:<version>")   // JUnit 5
    // or
    testImplementation("dev.kensa:kensa-kotest:<version>")  // Kotest runner

    // Assertions bridge (pick one or more)
    testImplementation("dev.kensa:kensa-kotest:<version>")
    testImplementation("dev.kensa:kensa-assertj:<version>")
}

Find the latest version on the releases page.

See the Kotlin quickstart or Java quickstart for a full setup walkthrough.

Tooling

CLI — serve reports locally

Every release ships pre-built binaries for macOS (Intel + Apple Silicon), Linux, and Windows. Download kensa-<os>-<arch> from the latest release, then:

kensa serve <path-to-report-dir>

This starts a local HTTP server and opens your HTML reports in the browser.

Claude Code skill — AI-assisted test review

Every release also ships kensa-test.skill, a Claude Code skill that reviews Kensa tests for idiomatic style, fluency violations, and best-practice patterns.

Install it once:

claude plugin install kensa-test.skill

Then invoke it in any Claude Code session:

/kensa-test review this test

The skill checks for fluent English in rendered test bodies, correct use of Fixtures and CapturedOutputs, semantic assertion naming, composable setup toolboxes, and the typed context/mixin pattern for multi-stub tests.