Testing Verification

Verify observable behavior at the narrowest reliable level, using project conventions and the failure cost to choose coverage.

Delegation

Run in the main conversation by default. Delegation can increase usage: obtain explicit approval for the proposed agent count and scope before using subagents. Reuse that approval within its bounds; ask again before expanding the approved count or scope.

Select evidence

Inspect relevant contracts, nearby tests, fixtures, commands, and CI definitions. Choose checks that can fail for the behavior in question, including important negative paths. Use test-strategy.md when the test level or coverage tradeoff is unclear.

Prefer existing test infrastructure and stable fixtures. Test public behavior rather than incidental implementation details; avoid hidden network dependencies, production data, and timing-based assertions. Add automation when it protects meaningful behavior, without writing tests that simply mirror trivial edits.

Browser work

Use the browser surface the host and project policy designate for interactive, exploratory, screenshot, and visual comparison work. If that surface fails, troubleshoot it before falling back to another, and say which surface produced the evidence. When the user named a specific surface, get their direction before substituting a different one.

Source-controlled Playwright E2E provides repeatable regression coverage. Keep it distinct from a manual Browser pass. Read ui-visual-verification.md when comparison conditions or visual ambiguity matter.