Testing
Implemented
The listed checks run locally. Full Hermit execution is not currently a CI gate.
Choose a check that exercises the changed boundary. A unit test can prove a pure transformation; it cannot establish PostgreSQL RLS, workload authentication or crash recovery.
| Change | Check | Why |
|---|---|---|
| App logic or UI | pnpm --filter kesita-app test, typecheck, lint | Exercise app behavior and compile-time boundaries |
| Go code | pnpm go:test, go:vet, go:lint | Race-enabled workspace tests plus static checks |
| Wire contract | pnpm contracts:generate, contracts:check-drift | Keep generated clients aligned with source schemas |
| Database schema/queries | pnpm db:check-drift and the relevant Hermit suite | Generated-code consistency and actual database behavior are different checks |
| Docs | pnpm --filter docs build | Validate status metadata, evidence paths and renderable content |
Hermit owns integration setup, suite selection and result inspection. Its plans and suite YAML are the source for exact tests and timeouts. scripts/check-integration-coverage.mjs checks discovery; .github/workflows/ci.yml currently validates and dry-runs Hermit without executing the full plan.
The release pipeline marks actual Hermit execution in CI as pending. A validated plan alone is not evidence that its suites passed.