Skip to main content

Testing And Release

Cross-repo release workflow

Use this page for system-level testing and release coordination across the mobile experience, admin control plane, and docs site.

Start with

  • QA Tester Guide for a guided manual validation path
  • Release Signoff Checklist for lightweight approval before broad sharing
  • Screenshot updates when UI or workflows change materially
Builder Insights operations flow illustration

Operations loop

Release confidence comes from one connected workflow

The strongest operational process is not just running checks. It is moving cleanly from setup, to testing, to reporting, to signoff, to docs updates, and then to release verification.

  • testing and documentation should reinforce each other
  • release confidence improves when evidence and signoff stay structured
  • post-change visual updates are part of the workflow, not extra polish

Testing lanes by repo​

Mobile app

Use repo-local validation plus manual verification for the device-dependent and trust-sensitive parts of the product.

  • install with npm install
  • run typecheck with npx tsc --noEmit
  • use focused Jest runs for data, store, and sync changes
  • perform manual verification for offline, auth, microphone, camera, biometrics, and uploads
Admin app

Use the admin repo to validate route behavior, operational workflows, and production-style build checks.

  • install with npm install
  • run local dev with npm run dev
  • run tests with npm test
  • run production build checks with npm run build
Docs site

Treat documentation updates as release-sensitive when they describe changed behavior or new visuals.

  • run npm run build after meaningful docs changes
  • verify screenshots, diagrams, and internal links still render
  • update visual guides when product behavior materially changes

Documentation updates during release work​

QA check

Update docs when behavior changes

  • update repo-local docs if implementation details changed
  • update this site if system-level or operational behavior changed
  • attach new screenshots if UI or workflows materially changed

Risk

Do not treat docs and screenshots as afterthoughts

When workflows, labels, dashboards, or expectations change, stale docs can undermine release confidence just as much as stale code comments or missing tests.