Skip to content
Wavemap Docs

Testing

Testing changes should start with one question: which layer gives the cheapest useful signal for the behavior being changed?

This section is the durable testing reference for Wavemap. Historical detail and older migration notes may still live in apps/wavemap-docs/working-notes/TESTING.md, but these pages are the reference surface to update when a testing convention settles.

Pages

Section titled “Pages”
PageUse It For
Testing OverviewLayer selection, command surfaces, and the current test surfaces.
Testing Authoring PatternsMocking boundaries, request and DB-backed recipes, front-end integration patterns, naming conventions, LLM prompts, and low-value coverage warnings.
Testing Runtime And CIBrowser E2E runtime contracts, Playwright preparation, CI jobs, i18n verification, manifest-backed checks, deployed-dev smoke, and docs smoke.

Quick Orientation

Section titled “Quick Orientation”
  • Start with Testing Overview when choosing the cheapest meaningful verification layer or command.
  • Use Testing Authoring Patterns when deciding how to mock, where to place a test, or which neighboring examples to imitate.
  • Use Testing Runtime And CI when the question involves Playwright, built runtimes, CI jobs, generated i18n assets, deployed smoke, or docs smoke.
Section titled “Related Pages”