kensa.dev

What It Is

Kensa is a modern BDD testing framework for Kotlin and Java. Its goal is to preserve the readability of Given-When-Then while avoiding the maintenance overhead of traditional Cucumber/Gherkin setups, such as feature files, step definitions, and mapping relationships. Tests are written directly in code, and after execution Kensa generates interactive HTML reports that include test sentences, captured values, fixture state, and optional sequence diagrams showing component interactions.

Core Capabilities and Ecosystem

Functionally, Kensa focuses on “code as specification.” Through KensaTest, it exposes a DSL with given, and, whenever, and then, while @RenderedValue automatically displays field values in reports. It supports JUnit 5, JUnit 6, and TestNG, and the documentation also lists Kotest-related integrations. Assertion libraries can include AssertJ, Hamcrest, HamKrest, and Kotest matchers. Its sequence diagram feature is particularly distinctive: it can capture interactions between components and let users drill down into payloads, headers, and metadata.

On the ecosystem side, Kensa provides a Gradle plugin, BOM, IntelliJ IDEA plugin, and TeamCity plugin. In TeamCity, reports can be embedded, with human-readable test names and failure summaries displayed. It also provides AI Agent Skills for Claude Code and OpenCode, as well as prompt-file based integration with tools such as Copilot and Cursor.

Pricing and Deployment

The captured content does not provide pricing, payment methods, or details about commercial services. Kensa works through dependencies, a Gradle plugin, and local/CI report output. Reports are written to a temporary directory by default, but a fixed path can also be configured. The TeamCity plugin can be installed on a self-hosted TeamCity server. The pages mention GitHub, source repository, releases, and related information, but do not clearly state the license, so its open-source status cannot be determined from the text alone.

Pros and Cons

The main advantage is that BDD expression lives directly in Kotlin/Java, reducing duplicate maintenance. Its HTML living documentation and sequence diagrams provide practical value for collaboration, troubleshooting, and review. IDE and CI integrations are fairly complete, and the documentation covers Quickstart, API, CLI, UI Testing, Integrations, and more, with clear examples.

The limitations are also clear: its scope is mainly the JVM ecosystem; the current version is v0.8.5, and the roadmap notes breaking changes in v0.7.x and v0.8.x, so upgrades should be handled carefully. Commercial support, SLA, and pricing information are missing. Some pages describe Kotest support somewhat inconsistently, so the actual support status should be verified against the specific version in use.

Who It’s For and Access from China

Kensa is suitable for Kotlin/Java teams, backend or platform teams that value readable test reports, and teams that want BDD without maintaining Gherkin files. The text does not describe access conditions from China. Related dependencies come from Maven Central, plugin marketplaces, and GitHub/JetBrains Marketplace, so actual availability may depend on the network environment. If access is unstable, alternatives such as Cucumber or native JUnit/Kotest-based testing setups may be worth considering.