How Validate.QA works

Three ways to give Validate.QA work, one consistent output: native @playwright/test .spec.ts files in your repo.

Path A · MCP — your AI editor calls our tools directly. Cursor, Claude Code, Codex.

Path B · Discovery — a headless agent surveys your live app from a single URL, plans coverage, and proves each spec against the running app.

Path C · Voice — narrate a browser flow with the Chrome extension. Whisper transcribes, the agent correlates speech to actions.

Selectors are picked with a deterministic 9-tier strategy: testid > role > label > placeholder > text > id > name > class > CSS path.

Assertions are proven against the running DOM before they are written. Tests that do not prove out are dropped, not hallucinated.