mcpField
P
playwright-qa

playwright-qa

github.com/testdino-hqTesting & quality405221 installsUpdated 2w ago
Repository

About playwright-qa

A set of Playwright workflow guides for QA engineers, covering test design, failure classification, manual-suite automation, and test review. It emphasizes boundary cases, traceable case IDs, and checking that tests can actually fail.

Key features

  1. 01Turn requirements into test cases and plans
  2. 02Classify app bugs, test bugs, and flakes
  3. 03Convert manual cases into Playwright specs
  4. 04Review tests and verify they can fail

Use cases

  1. 01Plan tests from tickets or acceptance criteria
  2. 02Triage failing tests and write bug reports
  3. 03Automate a manual suite from CSV cases
  4. 04Review Playwright tests or a pull request

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/testdino-hq/playwright-skill --skill playwright-qa

After installing, type/playwright-qain Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

bug-reports.md
manual-to-automated.md
test-design.md
test-review.md

Details

From the project README

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 doingGuide
Ticket / PRD / acceptance criteria → test cases, risk ranking, test plan for the generatortest-design.md
Failing test → app bug, test bug or flake; bug report; what to do with the test meanwhilebug-reports.md
Manual test cases or a CSV export → Playwright specs with case IDsmanual-to-automated.md
Review Playwright tests or a PR; lint rules; prove a test can failtest-review.md

Golden Rules

  1. Boundaries and negative paths first: bugs live at the edges of a rule, not in the happy path.
  2. Lowest layer that proves it: rules at API level, wiring and critical flows in E2E.
  3. Classify before filing: app bug, test bug, flake or environment; the trace usually decides.
  4. Frequency is a number: --repeat-each=20 gives N/20, never "sometimes".
  5. Known bug → test.fail() with an issue link, never a deleted test or a loosened assertion.
  6. A test that can't fail guards nothing: break the feature once and watch it fail.
  7. Keep case IDs on automated tests so results map back to the manual suite.

Comments

Markdown supported