Testing Verification

Use this skill when testing or verification is a meaningful part of the task. Prefer project evidence over generic test advice, and verify behavior at the narrowest reliable level before broadening.

Operating Rules

• Read project instructions, docs, existing test conventions, package scripts, CI config, and nearby tests before adding or changing tests.
• Use the project's existing test tools and naming conventions.
• Test behavior and contracts, not implementation details, unless the project already expects lower-level tests.
• Prefer targeted verification first, then broader suites when practical.
• Do not add a new testing framework unless the project has no reasonable existing path and the benefit is clear.
• Keep tests maintainable: small setup, clear assertions, stable fixtures, no hidden network or production dependencies.
• For UI work, prefer real-browser verification and element-level screenshots before full-page screenshots.
• When user-provided UI images are ambiguous, annotate unclear areas with labeled circles/arrows and ask before coding.

Workflow

1. Discover Test Sources