Overview

Guides and practices for integration testing, system testing, performance testing, security testing, and test environment management.

Pages in this section

Page	What it covers
Checks That Cannot Fail	Deriving a check’s answer from a fact the failure cannot produce, with seven worked instances
End-to-End Tests Against a Real Deployment	Standing up a Playwright suite against a live tenant: opt-in, server ownership, residue, subject identity, credentials
Reading Evidence in a Codebase	The same rule for searches, counts and claims about a tree: inert patterns, names versus bindings, citing the ref
What a Green Run Proves	The same rule for gates and suites: the corpus a run visited, self-derived fixtures, instruments never shown to fail
What a Gate Must Declare	What a verdict must say about itself to be auditable: its denominator, its scope, that it can fail, and the artifact it measured
Backend Testing	Kotlin tests with Kotest, MockK, ContainerizedPostgres and LocalStack
Frontend and Backend Testing Patterns	Tool-scoped recipes for MockK, Kotest, Jest and React Testing Library
API Testing with Bruno	Writing the Bruno collections that exercise a component’s HTTP surface
Running API Tests	Executing those collections against a local or deployed component

See also

• Test-Driven Development — the rule for all implementation work: tests first, seen failing, then the implementation, and what a red run has to look like to count. Lives under implementation/; the discipline it describes is why most of the pages above exist.