Browser QA — Automated Visual Testing & Interaction When to Use - After deploying a feature to staging/preview - When you need to verify UI behavior across pages - Before shipping — confirm layouts, forms, interactions actually work - When reviewing PRs that touch frontend code - Accessibility audits and responsive testing How It Works Uses the browser automation MCP (claude-in-chrome, Playwright, or Puppeteer) to interact with live pages like a real user. Safety first — blast radius (run read-only by default) Browser QA drives real auth and real user journeys, so treat the blast radius expli…