QA Browser Automation

The agent drives Chrome MCP for live browser testing and uses four Python tools for deterministic health scoring, accessibility auditing, visual regression tracking, and report generation.

Clarify First

Before the QA sweep, confirm these inputs. If any is unknown or vague, ASK — do not assume:

• Target URL/app + auth — what to test and how to log in (the subject of the entire sweep)
• Testing tier — Quick / Standard / Deep / Exhaustive (sets scope, breakpoints, and duration)
• Fix autonomy — auto-fix P3/P4 and commit, vs report-only / ask before any code change (changes whether the working tree is modified)
• WCAG target level — A / AA / AAA (sets the accessibility pass bar)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Quick Start