Test an AQE Change
- Read
AGENTS.md, the changed code, nearby tests, and relevant public interfaces. - Reproduce a reported defect with the exact scenario before changing code.
- Identify the affected QE specialty from references/test-specialties.md.
- Add tests in this order:
- durable boundary contracts, invariants, or properties;
- integration behavior across affected components;
- focused unit examples needed for the red-green loop.
- Keep tests deterministic. Do not hide failures with retries, skips, weakened assertions, fabricated fixtures, or mocks of the behavior under test.
- Run the narrowest matching Vitest target first. Expand to typecheck, build, agent/skill parity, MCP integration, or full CI checks in proportion to the changed surface.
- For capabilities exposed through both CLI and MCP, verify both paths.
- Report commands, pass/fail counts, limitations, and untested external dependencies.
Never modify or reset .agentic-qe/memory.db. Use a copy for any database test.