qa-browser-ui-verification

Name: qa-browser-ui-verification
Availability: InStock
Author: fernansuoza

Verify web application behavior with Playwright or Cypress UI tests.

Updated Mar 22, 2026

Search Tags:#accessibility #playwright #cypress #ui-testing #e2e-testing #cross-browser #test-automation

Ready to run

npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill qa-browser-ui-verification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-browser-ui-verification
Source: https://github.com/FernanSuoza/AIDD-project-bootstrap/tree/main/templates/skills/qa-browser-ui-verification
Command: npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill qa-browser-ui-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browser-facing features are brittle, flaky, or under-tested and lack reproducible evidence tied to requirements; this Skill provides patterns and practices to verify user-visible web behavior reliably and capture actionable evidence for stories and bugs.

Core Features & Use Cases

Resilient UI automation: guidance for Playwright and Cypress patterns that reduce flakiness and enforce test isolation.
Evidence capture: capture traces, screenshots, recordings, and focused assertions that map back to requirements and stories.
Accessibility and cross-browser checks: combine automated a11y scans and multi-browser runs to reveal regressions across supported environments.

Quick Start

Use the qa-browser-ui-verification skill to run or author Playwright or Cypress tests, collect traces and screenshots, and attach the evidence to the related story or bug.

Frequently Asked Questions about qa-browser-ui-verification

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

FAQPage Schema

How do I reduce flakiness in Playwright and Cypress end-to-end tests?▼

To reduce flakiness in Playwright and Cypress tests, apply resilient UI automation patterns that enforce test isolation and capture trace artifacts, ensuring reliable browser behavior verification.

How do I capture screenshots and traces as evidence for bug reports?▼

Capture screenshots and traces as evidence by running UI verification automation that records execution artifacts and maps focused assertions directly to linked story requirements.

Does this approach support automated accessibility and cross-browser testing?▼

Automated accessibility and cross-browser testing are supported by combining a11y scans with multi-browser runs to reveal regressions across all supported environments.

Can I use network stubbing with Playwright or Cypress for test isolation?▼

Network stubbing with Playwright or Cypress is supported for test isolation, allowing controlled end-to-end web flow execution and capture of reproducible evidence.

What is the best way to link UI test automation results to user stories?▼

The best way to link UI test automation results to user stories is to capture focused assertions, screenshots, and traces during execution and attach the evidence directly to related bugs.