Skip to content
Skills Library
Programming · Testing

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.

Licence
MIT
Last repository change
10.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

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

  1. Principles
  2. Steps
  3. Output
  4. Red flags to refuse
Original SKILL.md headings · 24 lines, 223 words
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

RepositoryScoreLicence
This page · RobinBeraud/claude-qa-skills90MIT
5dive-ai/skills100MIT
market0v0/shipkit100MIT
hmislk/hmis98GPL-3.0
helx0071/skillsmo90MIT

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.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.