skills.rest
mirzadham
mirzadhamCOMMUNITY
Explore all skills by this author →
GitHub

browser-qa

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

Updated May 7, 2026
Search Tags:#accessibility#qa#web vitals#browser automation#regression testing#playwright#visual testing
One-click install
npx skills add https://github.com/mirzadham/trainingroombookingsystem2 --skill browser-qa-mirzadham
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-qa
Source: https://github.com/mirzadham/trainingroombookingsystem2/tree/main/.pi/skills/browser-qa
Command: npx skills add https://github.com/mirzadham/trainingroombookingsystem2 --skill browser-qa-mirzadham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually verifying that a deployed feature actually works across pages, viewports, and user journeys is slow and error-prone. This Skill automates post-deploy QA by driving a real browser to catch console errors, broken links, layout 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 & Journey Testing: Clicks navigation links, submits valid and invalid form data, and exercises auth flows and critical user journeys with read-only safety defaults. - Visual Regression & Accessibility: Captures screenshots at 375px, 768px, and 1440px breakpoints, compares against baselines, and runs axe-core WCAG 2.2 AA audits. - Use Case: After deploying a new checkout page to staging, run this Skill to verify forms, screenshots, and accessibility, then receive a structured QA report with a SHIP / SHIP WITH FIXES / DO NOT SHIP verdict. ## Quick Start Run a browser QA pass on the staging deployment at https://staging.example.com and report any console errors, broken interactions, visual regressions, 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 375px, 768px, and 1440px breakpoints, and compare them against committed baseline screenshots. Flag layout shifts over 5px, missing elements, and overflow issues in the report.

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 MCP that can navigate pages, capture screenshots, and inspect console and network activity works.

Can I run automated QA tests against a production site?▼

Yes, but only in read-only mode by default. Mutating journeys like checkout, payment, or deletion require explicit opt-in and a staging or preview URL, using seeded test credentials rather than real production logins.

Does axe-core catch all accessibility violations?▼

No. axe-core automatically covers roughly 30-40% of WCAG criteria. A clean automated run is necessary but not sufficient; keyboard navigation, focus order, and screen reader checks still require manual verification.

What happens if there is no baseline screenshot for visual regression?▼

Without a committed baseline, visual regression comparison is impossible, so the report verdict is marked INCONCLUSIVE rather than a silent pass. Capture and commit baselines first to enable meaningful comparisons.

Related Skills

Explore More Software Engineering Skills→
wagnerra23wagnerra23

criar-staging

Clone production into a staging environment with an anonymized MariaDB instance.

Community
Advanced
TumeloRamaphosaTumeloRamaphosa

canary

Monitors live applications after deployment for console errors, performance regressions, and page failures.

Community
Intermediate
kdlbskdlbs
562

verify

Run format, typecheck, tests, and lint across monorepo packages.

Official
Intermediate
mgd34msumgd34msu
4

storybook

Develop, document, and test UI components in isolation with Storybook.

Community
Intermediate