Tab · Build
Tests
Know exactly which tests run on which PR, and where to add a new one. Every test suite, runner, fixture, and CI job — what it covers, where it lives, when it runs.
See it in motion
Where to find it
- Localhost:
/tests.html?repo=<id> - On disk:
.claude/brain/tests.md - Keyboard: ⌘ K then
tests - Sidebar: Build → Tests
What it does for you
One inventory of every test in the repo.Each suite has a row: runner, scope (unit/integration/e2e), trigger (PR / nightly / release), and the CI job name. No more “wait, is that one even running?”
Adding a test is a known motion.The doc tells you where to add a unit test, an integration test, a CI gate. Pick the right home; don't scatter test files across the repo.
CI gates are listed by name.Every required check (twin-drift, brain-record, website-build) is enumerated with its purpose, so a red square has an obvious next step.
Configure
Tests live where the doc says. CI jobs are defined in .github/workflows/ and listed here for reference.
Use it well
When you add a CI job, add the row here in the same PR. When you change a job's trigger, update the row. The doc is the source of truth for “what gates the merge.”