AGENTS.md@tests · git:20261003.a4f7a04 · 2026-10-03 · sha256 8383c85693d8410b
AGENTS.md@tests git:20261003.a4f7a04A
Immutable. This exact content never changes and is served at /api/v1/blob/8383c85693d8410b.
# Tests Behavioral and integration tests for the plugin. Bun specs (`*.spec.ts`) live beside the code they cover, such as `servers/`, `src/` and `scripts/`, rather than here; mod tests are in `mod/`. ## Layout - `fixtures/mcp/`: JSON-RPC requests and the golden `expected-tools.json` baseline, which `servers/omca.spec.ts` and the validator's MCP check read. - `fixtures/boulder-schemas/`: sample `boulder.json` shapes for registry tests. - `fixtures/plans/`, `fixtures/settings/` and `fixtures/statusline/`: a long plan file for the plan reader spec, the settings files status line setup reads, and the recorded payload and output cases of the status line. - `fixtures/spec-env.ts` and `fixtures/fake-exec.ts`: helpers for specs that spawn a process, one for the environment to pass and one for a fake executable that works on Windows. - `fixtures/canonical-tmp.ts` and `fixtures/plain-output.ts`: the `bunfig.toml` preloads. The first gives every spec the long form of `TEMP` on Windows, the second drops `FORCE_COLOR`. - `mod/`: the mod tests, run by `claude plugin test .`. `mod/visual/` holds the view definitions and the recorded captures behind `just visual <view>`. - `evals/`: eval task definitions for agent-quality checks under `evals/tasks/`, listed by `bun scripts/qa/eval-tasks.ts`. `evals/unscored/` holds fixtures whose criteria need judgment, and `evals/results/` the trial records and the running turn count. `evals/README.md` has the procedure. - `plugin-evals/`: `claude plugin eval` cases for the planning skills' health gate. They call a real model, so they run by hand. `plugin-evals/README.md` has the commands. - `README.md`: how to run and add tests in each layer. Read it before this file for how-to details. ## Conventions The state files these tests exercise are written under `.omca/state/` (and `.omca/evidence/` for the evidence log). `fixtures/boulder-schemas/` holds the `boulder.json` shapes, and `src/core/boulder.ts` is the authority on that schema.