API Overview
Overview of Kensa's public API covering the Given-When-Then DSL, framework integrations (JUnit 5 & 6, Kotest, TestNG), and assertion library mixins.
Configuration
Complete reference for configuring Kensa — output directory, issue tracker URL, report layout, sentence parsing, custom renderers, and source locations.
Fixtures
How to define and use Kensa Fixtures — type-safe, lazily-created test data shared across given, whenever, and then steps, with support for dependent fixtures and highlighted values.
Factory Fixtures
Parameterised fixture factory functions — call a @Fixture-annotated factory inline in a test with a parameterised-test parameter, and Kensa renders the seeded, argument-derived value as a fixture token.
Attachments
How to attach typed plugin-defined data to a test for display in custom report tabs.
Captured Outputs
How to use CapturedOutputs to store and retrieve values produced during the whenever step, with typed and string keys, and highlighting support.
Setup Steps
SetupStep: reusable, named test setup with the givens/actions/verify triple and the imperative setup(scope) API.
Annotations
Reference for all Kensa annotations, covering value rendering, sentence structure, report notes, issue linking, and UI behaviour overrides.
Assertion Bridges
Reference for the four assertion-library bridges (Kotest, Hamkrest, Hamcrest, AssertJ) - artifacts, what each then / thenEventually / thenContinually accepts, SetupStep flavours, and what each one brings onto the classpath.
Async Assertions
Reference for thenEventually and thenContinually — polling assertions for asynchronous behaviour, with timeout, interval and initial-delay tuning.
Interaction Renderers
How to implement and register InteractionRenderer to control how exchanged values appear in Kensa's Captured Interactions tab and sequence diagrams.
Sentence Hints
Reference for Kensa's comment directives — ReplaceSentence and Ignore hints, and /// statement notes.
Log Tabs
How to surface external log output — files or Docker container stdout — in a per-invocation report tab, correlated to each test by a tracking identifier.