Kensa

See it in action

This is a real test from the Clearwave example, and below it the report it produced, live. Click around: open an interaction, read a payload, follow a value back to its fixture.

Write this…

OrderServiceTest.kt
@Test
fun `voice and broadband order is successfully completed`() {
    given(openNetworkWillCompleteTheOrder())
    and(fibreVisionWillCompleteTheOrder())

    whenever(aVoiceAndBroadbandOrderIsPlaced())

    then(theOrderConfirmation(), shouldBePending())
    thenEventuallyAllNotifications(
        shouldShowBothSuppliersCompletedSuccessfully(
            voiceSupplier = fixtures[voiceSupplier],
            broadbandSupplier = fixtures[broadbandSupplier],
        )
    )
}

…get this

Loading the live report…

Open the full report in a new tab →

For the people who can’t read the code

Testers, analysts and product owners get a report that says what the system did: Given–When–Then sentences with this run’s real values, every message that crossed between services, and a sequence diagram drawn from them. Open any interaction and read the payload.

For the developer writing it

Ordinary Kotlin or Java on JUnit 5 & 6, Kotest or TestNG, with the assertions you already use. No feature files, no step definitions, nothing to keep in sync. Refactor and the report follows, because the report is generated from the test that ran.

For the system you actually ship

Built for acceptance tests that sit outside a deployed application. Push a message in, watch what comes out, and let the report show the traffic. Link each test to its ticket with @Issue and the specification, the test and the evidence are one thing.

Plugins & Integrations

Surface Kensa output where your team already works.

IntelliJ Plugin

Open reports from your IDE

Open any Kensa test report in your browser directly from IntelliJ IDEA.

Gutter icons on test functions
Links in test console output
Test toolbar actions

View on JetBrains Marketplace →Docs

TeamCity Plugin

Reports inside your CI

Embed Kensa reports, GWT test names, and failure narratives directly in TeamCity builds.

Kensa Report tab on every build
Given-When-Then test display names
Failure summaries with captured state