browser-qa

Automate visual regression testing and UI interaction verification for web applications.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill browser-qa-zescode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-qa
Source: https://github.com/ZESCODE/Zes-Orchestration-System/tree/main/.agents/skills/browser-qa
Command: npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill browser-qa-zescode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of manual regression testing by automating the verification of UI layouts, user interactions, and accessibility standards across different viewports.

Core Features & Use Cases

  • Visual Regression: Automatically compares current page screenshots against committed baselines to detect layout shifts or missing elements.
  • Interaction Testing: Validates critical user journeys like form submissions, navigation, and authentication flows.
  • Accessibility Audits: Performs automated checks for WCAG 2.2 AA compliance, including contrast and focus order.

Quick Start

Use the browser-qa skill to run a full smoke test and accessibility audit on the staging URL provided in the current context.

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 for web applications?

Automate visual regression testing by capturing multi-viewport screenshots of web applications and comparing them against committed baselines to detect layout shifts or missing elements post-deployment.

Can I run automated accessibility audits for WCAG compliance?

Automated accessibility audits perform checks for WCAG 2.2 AA compliance, validating contrast and focus order to ensure web frontend stability and accessibility standard adherence.

How do I verify form submission and authentication flows without manual testing?

Verify form submission and authentication flows by automating critical user journeys through headless browser interactions, validating navigation and form submissions without manual regression testing.

Does browser-qa work with Playwright or Puppeteer?

Browser-qa works with Playwright, Puppeteer, or Chrome-based MCP interfaces, requiring these browser automation tools to execute headless browser interactions for UI verification.

What is the best way to test frontend stability across different viewports?

Test frontend stability by executing multi-viewport screenshots that capture layout states, then compare current captures against committed baselines to detect visual regressions across different screen sizes.

When do I need automated UI interaction verification after deployment?

Automated UI interaction verification is needed post-deployment to validate critical user journeys and ensure frontend stability, replacing manual regression testing with multi-viewport screenshot comparison.