browser-qa

Automates visual testing and UI interaction verification on deployed web pages using browser automation.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill browser-qa-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-qa
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/browser-qa
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill browser-qa-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually verifying that a deployed feature actually works across pages, viewports, and user flows is slow and error-prone. This Skill automates post-deployment QA by driving a real browser through smoke tests, interaction checks, visual regression, and accessibility audits. ## Core Features & Use Cases - Smoke Testing: Navigates to a target URL, checks console errors, network failures, and Core Web Vitals (LCP, CLS, INP). - Interaction Testing: Clicks nav links, submits forms with valid and invalid data, and exercises auth flows and critical user journeys. - Visual Regression & Accessibility: Screenshots pages at 375px, 768px, and 1440px breakpoints, flags layout shifts, and runs axe-core WCAG AA checks. - Use Case: After deploying a new checkout page to staging, run this Skill to confirm forms validate correctly, no console errors appear, mobile layout does not overflow, and accessibility violations are reported before shipping. ## Quick Start Run a browser QA pass on https://staging.example.com and report console errors, broken interactions, visual issues, and accessibility violations.

Frequently Asked Questions about browser-qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate visual testing after deploying a feature?▼

Use browser automation to navigate to the deployed URL, capture screenshots at multiple breakpoints (375px, 768px, 1440px), and compare against baselines. Flag layout shifts over 5px, missing elements, and overflow issues in a structured QA report.

What tools can I use for browser automation testing?▼

This workflow supports claude-in-chrome MCP tools (using your actual Chrome), Playwright via browserbase MCP, or direct Puppeteer scripts. Any of these can drive page navigation, form submission, and screenshot capture.

How do I test form validation and auth flows automatically?▼

Submit forms with valid data to verify success states and with invalid data to verify error states. For auth, automate the full login, protected page access, and logout sequence, then confirm each step behaves as expected.

Does browser QA testing check accessibility compliance?▼

Yes, the workflow runs axe-core or an equivalent scanner on each page to flag WCAG AA violations such as contrast issues, missing labels, and focus order problems. It also verifies keyboard navigation and screen reader landmarks.

What Core Web Vitals thresholds should a page pass?▼

The smoke test checks LCP under 2.5 seconds, CLS under 0.1, and INP under 200 milliseconds. Pages failing these thresholds are flagged in the QA report alongside console errors and failed network requests.