Skip to content
Developer docs

Testing

Use focused tests for fast feedback, then widen verification to the full user journey and production surface.

Run the quality gates

pnpm typecheck
pnpm test
pnpm --dir frontend lint
pnpm --dir frontend typecheck
pnpm --dir frontend test:e2e
pnpm build:site

Run the narrowest relevant check while iterating, then run the complete set before merging. A green unit suite does not prove that a browser journey, generated docs route, or deployment asset works.

Test by boundary

Domain and application

Test invariants, transitions, authorization decisions, and failure paths without SQLite or Fastify.

Repositories and routes

Verify persistence mappings, validation, stable error envelopes, authentication, and request correlation.

Frontend

Cover loading, empty, error, form validation, cancellation, keyboard, and responsive states.

Website

Build all static routes, inspect links against the configured base path, and verify docs navigation.

Before opening a change

  1. Add a regression test for the failure or behavior that motivated the change.
  2. Confirm external inputs still use Zod schemas and public responses remain compatible.
  3. Run the browser flow when a route, auth boundary, form, or navigation path changes.
  4. Run the site build when copy, docs, assets, or internal links change.
  5. Record any required migration, environment variable, or rollback step in the docs.

Read the contribution quality bar →