write-playwright-test
/write-playwright-test
Use when asked to write, add or change Playwright tests in this repo. Gives the exact steps and conventions so every test is reviewed, uses page objects, and is proven to fail when the app is wrong.
- Author
- shaharyaramjad ↗
- Repository
- ai-qa-copilot ↗
- Licence
- MIT
- Last repository change
- 02.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 02.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when asked to write, add or change Playwright tests in this repo. Gives the exact steps and conventions so every test is reviewed, uses page objects, and is proven to fail when the app is wrong.
Original author description
Use when asked to write, add or change Playwright tests in this repo. Gives the exact steps and conventions so every test is reviewed, uses page objects, and is proven to fail when the app is wrong.
How it works
- Steps
- Never
SKILL.md preview
--- name: write-playwright-test description: Use when asked to write, add or change Playwright tests in this repo. Gives the exact steps and conventions so every test is reviewed, uses page objects, and is proven to fail when the app is wrong. --- # Write a Playwright test (this repo) ## Steps 1. Read the approved test cases in `docs/test-cases/<feature>.md` or the plan in `specs/`. Do not invent cases. 2. Read `AGENTS.md` and the existing page objects in `pages/`. Reuse methods. Add a method to a page object if one is missing; never put selectors in a spec. 3. Open the real app (Playwright MCP tools) to confirm texts, URLs and values before asserting them. 4. Write `tests/<feature>.spec.ts`: one behavior per test, name starts with the ID, e.g. `TC-CART-08 ...`. 5. Run `npm run gate` (typecheck + whole suite). Fix failures in selectors or timing only. 6. Prove the test can fail: `npm run break-check -- tests/<file> <TEST-ID>` must end with `RESULT: PASS`. 7. Report: tests added, gate result, break-check result. Stop and wait for review. ## Never - Edit an expected value, remove an assertion, add `test.skip`/`fixme` or retries to get green. - Use `waitForTimeout` or fixed sleeps. Give slow pages a longer timeout on the assertion instead. - Read or print `.env`.
Versions
The database has no other skills named write-playwright-test.
Database snapshot: 13.11.2026 · package version bd745b81155c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100generate
Generate Playwright tests. Use when user says "write tests", "generate tests", "add tests for", "test this component", "e2e test", "create test for", "test this page", or "test this feature". - 100generate
Generate Playwright tests. Use when user says "write tests", "generate tests", "add tests for", "test this component", "e2e test", "create test for", "test this page", or "test this feature". - 100generate
Generate Playwright tests. Use when user says \"write tests\", \"generate tests\", \"add tests for\", \"test this component\", \"e2e test\", \"create test for\", \"test this page\", or \"test this feature\". - 100generate
Generate Playwright tests. Use when user says "write tests", "generate tests", "add tests for", "test this component", "e2e test", "create test for", "test this page", or "test this feature". - 100playwright-test-writer
Write or extend Playwright end-to-end tests for a web page or feature. Use when the user asks to add, write, improve or fix Playwright, e2e or browser tests. - 100playwright-testing
Write and maintain end-to-end tests with Playwright. Use when someone asks to "add e2e tests", "test my web app", "set up Playwright", "write browser tests", "test login flow", "visual regression testing", "test across browsers", or "automate UI testing". Covers test setup, page…