Docs
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
- Desktop:
localhost:4000, then Memory in the sidebar, then Reference index under All tools, in the Lessons, wiki and patterns group, which lists it. - Hosted:
repoops.ai/team/reference, from Memory in the sidebar, then Reference index under All tools, in the Lessons, wiki and patterns group, which lists it. - Keyboard: ⌘ K, then type “Tests”.
- On disk:
.claude/brain/tests.md
What it does for you
One inventory of every test in the repo.Every suite is listed with what it covers and where it lives, plus a layer table mapping unit, integration, and end-to-end tests to their runner and location. 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.
Suites name the CI job that runs them.A suite row names its gate where it has one, such as the
website-build job for the website tests and the brain-drift family for the structural checks, so a red square points at a suite. The full list of required checks lives in .github/workflows/ci.yml.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.”
Read more
Last updated