browser-qa

Automates visual testing, interaction verification, and accessibility audits on deployed web pages using browser automation.

2|Updated Mar 29, 2015
One-click install
npx skills add https://github.com/ovisan/dotfiles --skill browser-qa-ovisan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-qa
Source: https://github.com/ovisan/dotfiles/tree/main/.agents/skills/browser-qa
Command: npx skills add https://github.com/ovisan/dotfiles --skill browser-qa-ovisan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After deploying a feature, manually clicking through pages to verify layouts, forms, and interactions is slow and error-prone. This Skill automates post-deploy QA by driving a real browser to catch console errors, broken links, visual regressions, and accessibility violations before users do. ## Core Features & Use Cases - Smoke Testing: Checks console errors, failed network requests, and Core Web Vitals (LCP, CLS, INP) on desktop and mobile viewports. - Interaction & Visual Regression Testing: Exercises nav links, forms, and auth flows, then screenshots pages at 375px, 768px, and 1440px breakpoints to compare against baselines. - Accessibility Audits: Runs axe-core for WCAG 2.2 AA violations and verifies keyboard navigation, with explicit guidance that automated checks alone are not sufficient. - Use Case: After deploying a new checkout page to staging, run this Skill to verify the form submits correctly, screenshots match the baseline at all breakpoints, and no new accessibility violations were introduced — producing a SHIP / SHIP WITH FIXES / DO NOT SHIP verdict. ## Quick Start Run a browser QA pass on my staging deployment at the preview URL and report any console errors, broken interactions, visual regressions, and accessibility issues.

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 regression testing after deployment?

Screenshot key pages at three breakpoints (375px, 768px, 1440px) and compare them against committed baseline screenshots. Flag layout shifts over 5px, missing elements, and overflow. Without a baseline, report the result as inconclusive rather than a pass.

What browser automation tools work for UI testing?

This workflow supports claude-in-chrome MCP tools, Playwright via browserbase MCP, or direct Puppeteer scripts. Any browser automation MCP that can navigate pages, capture screenshots, and inspect console and network activity works.

Can I run automated browser tests against production safely?

Default to read-only journeys on production and never run mutating flows like checkout, payment, or deletion without explicit opt-in and a staging URL. Use seeded test credentials and redact tokens or PII before saving screenshots.

Does axe-core catch all accessibility issues?

No. axe-core automatically covers roughly 30-40% of WCAG criteria, so a clean run is necessary but not sufficient. Keyboard navigation, focus order, and screen reader checks still require manual verification before claiming a page is accessible.

What Core Web Vitals thresholds should a QA pass check?

Check LCP under 2.5 seconds, CLS under 0.1, and INP under 200 milliseconds. INP replaced FID as a Core Web Vital in March 2024, per web.dev thresholds.