← ClaudeAtlas

aeolus-fleet-testinglisted

Mandatory with behaviour-driven-development for every aeolus-fleet code change. Scope, paths, guarantees and what CI enforces.
ThomasHendrickx/aeolus-fleet · ★ 0 · Testing & QA · score 64
Install: claude install-skill ThomasHendrickx/aeolus-fleet
# Testing in aeolus-fleet (decision 0014) Load with `behaviour-driven-development`. - Strict for server and common; web: tests alongside. - Commit scope is the context: `test(<context>): <rule> (red)`. - Every test sits in a Vitest project of `vitest.config.ts`, named `<package>:<layer>` (unit, stories, integration, e2e); run a layer with `npm run test:<layer>`. Integration: `packages/core/test/*.integration.test.ts`, Testcontainers Postgres 16, covering the adapters, the raw SQL and the real composition. End to end: `e2e/*.e2e.test.ts`, the console in Chromium through Playwright against a real server and Postgres. - Guarantees: concurrent receivers never share a delivery; a forced mid-transaction failure stores nothing and wakes nobody; a restart loses nothing. - Boundaries include the 256 KB payload. Enforced by lint/CI (`eslint.config.js`, `scripts/`): a `feat` or `fix` commit touching production code comes right after a `(red)` commit with only tests (every other commit type passes), a test beside every use case, every test in a Vitest project, no `vi.mock`, no `vi.fn` or `vi.spyOn` in core and common. - Changed Prisma modules need a changed plan test importing the module and calling `assertIndexedPlan`; `scripts/check-query-plans.ts` checks this. For a change without a query, explain it as `None: <reason>` under `## Plans` in the PR.