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, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.

• 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).

Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.

Quick Start