API Overview

Kensa's public API is organised around a few core concepts. Start here, then dive into the reference pages below.

Core Concepts

Concept	What it does
Configuration	Global setup — output directory, issue tracker URL, custom renderers, and more
Fixtures	Type-safe, lazily-created test data shared across `given`, `whenever`, and `then`
Captured Outputs	Store and retrieve values produced during the action under test
Annotations	Control what appears in the HTML report — rendered values, notes, issues, and more

All framework integrations expose the same DSL via KensaTest:

Method	Context type	Purpose
`given(action)`	`Action<GivensContext>`	Set up fixtures and initial state
`and(action)`	`Action<GivensContext>`	Chain additional setup steps
`whenever(action)`	`Action<ActionContext>`	Exercise the system under test
`then(collector, matcher)`	`StateCollector<T>`	Assert on extracted state
`then(collector) { block }`	`StateCollector<T>`	Assert using a lambda block

Framework	Artifact	Registration
JUnit 5	`kensa-junit`	Automatic via ServiceLoader
Kotest	`kensa-kotest`	Manual — add `KensaKotestListener` in `ProjectConfig`
TestNG	`kensa-testng`	Automatic via ServiceLoader

Mix one or more interfaces alongside KensaTest to gain assertion methods: