playwright-qa
About
This Claude Skill helps QA engineers design, automate, and manage Playwright test workflows. It assists in creating test cases from requirements, writing bug reports from failures, converting manual tests to automated specs, and reviewing test code. Use it when you need to bridge QA processes and Playwright automation.
Quick Install
Claude Code
Recommendednpx skills add testdino-hq/playwright-skill -a claude-code/plugin add https://github.com/testdino-hq/playwright-skillgit clone https://github.com/testdino-hq/playwright-skill.git ~/.claude/skills/playwright-qaCopy and paste this command in Claude Code to install this skill
Documentation
Playwright QA Workflows
For QA engineers: the work around the test code. What to test, how to report what broke, how to automate a manual suite, and how to judge a test.
4 guides. They build on the core/ guides for the Playwright APIs and link to them rather than repeating them.
Guide Index
| What you're doing | Guide |
|---|---|
| Ticket / PRD / acceptance criteria → test cases, risk ranking, test plan for the generator | test-design.md |
| Failing test → app bug, test bug or flake; bug report; what to do with the test meanwhile | bug-reports.md |
| Manual test cases or a CSV export → Playwright specs with case IDs | manual-to-automated.md |
| Review Playwright tests or a PR; lint rules; prove a test can fail | test-review.md |
Golden Rules
- Boundaries and negative paths first: bugs live at the edges of a rule, not in the happy path.
- Lowest layer that proves it: rules at API level, wiring and critical flows in E2E.
- Classify before filing: app bug, test bug, flake or environment; the trace usually decides.
- Frequency is a number:
--repeat-each=20gives N/20, never "sometimes". - Known bug →
test.fail()with an issue link, never a deleted test or a loosened assertion. - A test that can't fail guards nothing: break the feature once and watch it fail.
- Keep case IDs on automated tests so results map back to the manual suite.
GitHub Repository
Frequently asked questions
What is the playwright-qa skill?
playwright-qa is a Claude Skill by testdino-hq. Skills package instructions and resources that Claude loads on demand, so Claude can perform playwright-qa-related tasks without extra prompting.
How do I install playwright-qa?
Use the install commands on this page: add playwright-qa to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.
What category does playwright-qa belong to?
playwright-qa is in the Testing category, tagged ai, testing, automation, and design.
Is playwright-qa free to use?
Yes. playwright-qa is listed on AIMCP and free to install.
Related Skills
This Claude Skill runs the lm-evaluation-harness to benchmark LLMs across 60+ standardized academic tasks like MMLU and GSM8K. It's designed for developers to compare model quality, track training progress, or report academic results. The tool supports various backends including HuggingFace and vLLM models.
This skill provides comprehensive knowledge for implementing Cloudflare Cron Triggers to schedule Workers using cron expressions. It covers setting up periodic tasks, maintenance jobs, and automated workflows while handling common issues like invalid cron expressions and timezone problems. Developers can use it for configuring scheduled handlers, testing cron triggers, and integrating with Workflows and Green Compute.
This Claude Skill provides a Playwright-based toolkit for testing local web applications through Python scripts. It enables frontend verification, UI debugging, screenshot capture, and log viewing while managing server lifecycles. Use it for browser automation tasks but run scripts directly rather than reading their source code to avoid context pollution.
This skill helps developers complete finished work by verifying tests pass and then presenting structured integration options. It guides the workflow for merging, creating PRs, or cleaning up branches after implementation is done. Use it when your code is ready and tested to systematically finalize the development process.
