Operations

Operational guidance for running behavioural verification consistently across local development and automation.

Repeatable local and CI runs

Run npx testkit run from the repository root. Testkit acquires the selected managed engine, starts declared local services, and schedules suite files. It manages k6, Node/Vitest, and Playwright runtimes, so consumers do not configure system engine paths.

Results and artifacts

Every terminal run is sealed under .testkit/results/runs/<run-id>/ with canonical run metadata, provenance, a manifest, logs, and artifacts. Payloads are SHA-256-addressed under .testkit/results/objects/sha256. Archive .testkit/results/ in CI to retain inspectable evidence.

Managed resources

For services configured with local Postgres, Testkit provisions Docker-managed databases. Use npx testkit destroy for current-product resources. Use npx testkit cleanup --resources --global --dry-run before global cleanup; remove --dry-run only after reviewing the proposed resources.