playwright-e2e
/playwright-e2e
Write or fix Playwright end-to-end tests (TypeScript or Python) with user-facing locators, web-first assertions, isolated test data and no fixed sleeps, then run them and iterate until they pass for the right reason. Use when asked for UI/E2E tests, to automate a scenario, or to stabilise a failing Playwright test.
- Author
- RobinBeraud ↗
- Repository
- claude-qa-skills ↗
- Licence
- MIT
- Last repository change
- 10.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 10.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
Write or fix Playwright end-to-end tests (TypeScript or Python) with user-facing locators, web-first assertions, isolated test data and no fixed sleeps, then run them and iterate until they pass for the right reason. Use when asked for UI/E2E tests, to automate a scenario, or to stabilise a failing Playwright test.
Original author description
Write or fix Playwright end-to-end tests (TypeScript or Python) with user-facing locators, web-first assertions, isolated test data and no fixed sleeps, then run them and iterate until they pass for the right reason. Use when asked for UI/E2E tests, to automate a scenario, or to stabilise a failing Playwright test.
How it works
- Principles
- Steps
- Output
- Red flags to refuse
SKILL.md preview
--- name: playwright-e2e description: "Write or fix Playwright end-to-end tests (TypeScript or Python) with user-facing locators, web-first assertions, isolated test data and no fixed sleeps, then run them and iterate until they pass for the right reason. Use when asked for UI/E2E tests, to automate a scenario, or to stabilise a failing Playwright test." --- # Playwright end-to-end tests ## Principles - **Locators users see**: `getByRole`, `getByLabel`, `getByText`, `getByTestId` as a last resort. No CSS chains, no XPath. - **Web-first assertions** that auto-wait: `await expect(locator).toHaveText(...)`. Never `waitForTimeout`. - **Independent tests**: each test creates its own data (API or fixture) and does not depend on order. - **Authenticate once** with `storageState`, not through the login form in every test. - **Mock only third parties** you do not own (`page.route`), never your own backend in an E2E test. - One user journey per test; keep the pyramid: logic belongs in unit/API tests. ## Steps 1. Read the scenario (Gherkin or steps) and the app's existing test setup (`playwright.config`, fixtures, page objects). 2. Write the test with the conventions above; add a page object only if the screen is reused. 3. Run: `npx playwright test path --reporter=line` (or `pytest` for Python). Read failures and traces (`--trace on`). 4. Fix the **cause**: missing wait condition, wrong locator, shared data. Never add a sleep. 5. Run 5 times in a row (`--repeat-each=5`) to prove stability before handing over. ## Output The test file, the commands run with their output, and the stability result. Mention anything you mocked. ## Red flags to refuse `waitForTimeout`, `force: true` clicks to bypass overlays, `test.retry` used to hide a real race, assertions on CSS classes instead of behaviour.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · RobinBeraud/claude-qa-skills | 90 | MIT |
| 5dive-ai/skills | 100 | MIT |
| market0v0/shipkit | 100 | MIT |
| hmislk/hmis | 98 | GPL-3.0 |
| helx0071/skillsmo | 90 | MIT |
Database snapshot: 13.11.2026 · package version 018b9af09791 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100playwright-generate-test
Generate Playwright TypeScript tests based on a scenario using Playwright MCP for real browser interaction. Use when the user wants to create an end-to-end test, generate a test from a user story, or automate a test scenario with Playwright. - 100v1-e2e-testing
Use when implementing or debugging browser end-to-end tests, especially Playwright or flaky tests. Triggers on "E2E test", "Playwright", or "flaky browser test". - 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. - 95playwright-test
Creates Playwright browser-based end-to-end tests for Next.js pages covering complete user journeys from start to finish. Use when the user asks to "write Playwright tests", "create e2e tests", "write integration tests", "test in the browser", or mentions end-to-end testing,… - 95playwright-e2e-tests
Write and maintain Playwright end-to-end tests for the Onyx application. Use when creating new E2E tests, debugging test failures, adding test coverage, or when the user mentions Playwright, E2E tests, or browser testing. - 100playwright-testing
UI/E2E test automation with Playwright MCP. Use when the user asks to "test the UI", "automate browser tests", "check the page", "take a screenshot", "run Playwright", "write E2E tests", or anything about browser-based testing.