qa-testing

Automate end-to-end testing, visual regression, accessibility audits, and GitHub issue creation with Playwright.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/aroido/vibesmith --skill qa-testing-aroido
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-testing
Source: https://github.com/aroido/vibesmith/tree/main/.cursor/skills/qa-testing
Command: npx skills add https://github.com/aroido/vibesmith --skill qa-testing-aroido

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the entire Quality Assurance process, from automated testing to bug reporting, significantly reducing manual effort and improving software quality.

Core Features & Use Cases

  • Automated E2E Testing: Run comprehensive end-to-end tests using Playwright across multiple browsers and devices.
  • Visual Regression Testing: Automatically detect UI changes and regressions using AI-powered diffing.
  • Accessibility & Performance Audits: Ensure WCAG compliance and optimal performance with integrated tools.
  • Bug Reporting Automation: Automatically generate detailed GitHub Issues with logs, screenshots, and test results.
  • Use Case: A developer pushes a new feature. This Skill automatically runs all E2E tests, performs visual regression checks, audits accessibility, and if any issues are found, it creates a detailed GitHub Issue with all necessary information for the developer to fix it.

Quick Start

Run a full QA session by executing the qa-session.sh script.

Frequently Asked Questions about qa-testing

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

FAQPage Schema
How do I automate end-to-end testing and visual regression checks with Playwright?

Automated end-to-end testing and visual regression are handled by running comprehensive Playwright sessions across browsers and devices, utilizing AI-powered diffing to automatically detect UI changes and regressions.

Can I automate accessibility and performance audits for WCAG compliance using Lighthouse and axe-core?

Accessibility and performance audits are automated by integrating axe-core for WCAG compliance checks and Lighthouse for optimal performance analysis, generating detailed audit reports for identified issues.

How do I automatically create GitHub issues for bugs and regressions found during testing?

Automated GitHub issue creation is facilitated by generating detailed bug reports that include logs, screenshots, and test results, requiring the GitHub CLI for full functionality during the QA session.

Do I need to install Playwright, axe-core, Lighthouse, and GitHub CLI before running QA automation?

Yes, Playwright, axe-core, Lighthouse, and GitHub CLI are required dependencies for full functionality, providing the environment for E2E tests, accessibility and performance audits, and automated bug reporting.

What is the best way to run a full QA session covering E2E tests, visual regression, and accessibility?

Running a full QA session is best achieved by executing the qa-session.sh script, which orchestrates end-to-end tests, visual regression checks, and accessibility audits into one automated workflow.

Are there limitations when using Playwright for automated UI visual regression testing across multiple browsers?

Limitations include ensuring consistent environments across multiple browsers and devices, as AI-powered visual regression diffing requires accurate baseline screenshots to correctly detect UI changes and regressions.