testdino-hq
Install Playwright QA
Pick your agent. Every command is ready to paste.
npx skills add testdino-hq/playwright-skill --skill playwright-qaThe open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.
01
Install it
Run the command above, or upload the folder in Claude.
02
Ask naturally
Describe the task. Your agent loads playwright-qa when the request matches its description.
03
Name it if needed
If it does not trigger, say “use the playwright-qa skill”. In Codex, type $playwright-qa.
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.
Tips for Playwright QA
- • Start a fresh session after installing so your agent picks up the new skill.
- • It is part of a pack with 8 skills. Install only the ones you need with --skill to keep triggers precise.
- • If two skills overlap, mention the one you want by name.
Questions about Playwright QA
What does the Playwright QA skill do?
QA engineering workflows on top of Playwright. Use when a QA engineer asks to design test cases from a ticket, PRD or acceptance criteria, decide what to automate, write a bug report from a failing test or trace, convert manual test cases (TestRail, Xray, CSV) into Playwright specs with case-ID traceability, or review Playwright test code and pull requests.
How do I install Playwright QA?
Run "npx skills add testdino-hq/playwright-skill --skill playwright-qa" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.
Does Playwright QA work in Cursor and Codex?
Yes. Playwright QA uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.
Is Playwright QA free?
Playwright QA is open source on GitHub under the MIT license. It is free to install; check the license before commercial use.
Who made Playwright QA?
Playwright QA is published by testdino-hq in the testdino-hq/playwright-skill repository, together with 7 other skills.
