QA Engineer

Tests running web applications via Playwright browser automation and reports P0-P3 findings.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/htxryan/claude-code-config-profiles --skill qa-engineer-htxryan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: QA Engineer
Source: https://github.com/htxryan/claude-code-config-profiles/tree/main/.agents/skills/compound/qa-engineer
Command: npx skills add https://github.com/htxryan/claude-code-config-profiles --skill qa-engineer-htxryan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes references (resource) components.

What problem does it solve? Automated unit and integration tests miss visual bugs, broken interaction flows, accessibility violations, and edge-case failures that only appear when a real user drives a live application. This Skill performs hands-on QA against a running app using browser automation, producing a structured severity-classified report. ## Core Features & Use Cases - Browser-driven testing: Controls a real browser via Playwright to run smoke tests, exploratory break-things testing, visual review, accessibility checks, form boundary testing, and network inspection. - Full application lifecycle handling: Detects the framework (Vite, Next.js, Django, Flask, FastAPI, Go), starts the dev server, waits for HTTP readiness, and cleans up processes afterward. - Structured QA report: Classifies every finding as P0-P3 with reproduction steps, screenshots, and documented passed checks. - Use Case: After building a new settings page, ask the agent to QA the running app — it will start the dev server, probe form fields with boundary and injection inputs, capture console errors and screenshots across breakpoints, and return a prioritized findings report. ## Quick Start Ask the agent to QA test the running application at localhost:3000 and report any bugs, accessibility issues, or visual problems it finds.

Frequently Asked Questions about QA Engineer

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

FAQPage Schema
How do I test a running web app with Playwright automation?▼

The skill detects your framework from package.json or project markers, starts the dev server, waits for HTTP readiness, then drives a headless Chromium browser through reconnaissance and test strategies. Findings are reported with severity levels and screenshots.

What does exploratory testing cover beyond automated tests?▼

It covers boundary inputs like empty strings and XSS payloads, state manipulation such as back-button after submission, auth edge cases, network throttling, and concurrency issues like double-click submits. These target failures that happy-path test suites miss.

Can this skill test accessibility and WCAG compliance?▼

Yes, it runs axe-core when available and maps violations to severity levels, or manually checks contrast ratios, keyboard navigation, ARIA labels, alt text, and heading hierarchy against WCAG 2.1 AA criteria.

What happens if the app fails to start or Playwright is missing?▼

Startup failures are reported as P1/INFRA findings with stderr diagnostics and remediation suggestions. If Playwright is missing, the skill attempts to install it once and retries before reporting infrastructure failure.

When should I use QA Engineer instead of automated test suites?▼

Use it when changes involve UI, visual behavior, or interaction flows that unit tests cannot verify. It complements automated tests by catching visual bugs, UX issues, and edge cases requiring human-like exploration of a live application.