e2e-testing-patterns skill (wshobson): Playwright and Cypress end-to-end test patterns for your agent
Gives your agent Playwright and Cypress patterns for writing end-to-end tests that do not flake.
- Installs
- 24.7K
- on skills.sh
- Stars
- 42.1K
- on GitHub
- Files
- 1
- besides SKILL.md
- Updated
- Oct 2026
- last repo commit
e2e-testing-patterns is a guidance skill by Seth Hobson from the wshobson/agents collection. When you ask for end-to-end tests, flaky-test fixes or a CI test pipeline, your agent follows its advice on what to test, selectors, waits, page objects and debugging.
A second file, references/details.md, holds worked Playwright and Cypress examples, including network mocking, visual regression, sharding and accessibility checks with axe. The skill bundles no scripts. Its examples show commands such as npx playwright test, which your agent runs only if you approve.
Good for
- Developers adding end-to-end tests to a web app
- Teams chasing flaky tests in CI
- QA engineers standardising on Playwright or Cypress
Install e2e-testing-patterns
Claude Code
- 1
Copy this prompt.
Install the e2e-testing-patterns skill in Claude Code. Run this command: npx skills add https://github.com/wshobson/agents --skill e2e-testing-patterns Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Node.js.
From its listing on skills.sh. Source.
What's in the skill
When it loads
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
Sections in SKILL.md
- When to Use This Skill
- Core Concepts
- 1. E2E Testing Fundamentals
- 2. Test Philosophy
- Detailed patterns and worked examples
- Best Practices
- Common Pitfalls
- Debugging Failing Tests
Key facts
- Installs on skills.sh
- 24,747 (data from 2026-11-02)
- Last repo commit
- 2026-10-30
- What is inside
- 2 files: SKILL.md and references/details.md, no scripts
What it includes
Critical journeys, complex interactions, auth, cross-browser
Says to keep E2E for login, checkout, signup, drag-and-drop and multi-step forms, and not for unit logic, API contracts or edge cases.
Try: “Which parts of this app deserve end-to-end tests, and which should stay unit tests?”
Read ·
What to test with E2ETest user behavior, keep tests independent, use data-testid
Eight best practices, including stable selectors, page objects, cleaning up test data and mocking for speed.
Read ·
Testing pyramid and best practicesFlaky waits, slow tests, coupled tests, poor selectors
Lists seven pitfalls and the fix for each, such as proper waits instead of fixed timeouts.
Read ·
Common pitfallsHeaded mode, debug mode, trace viewer, test.step, page.pause
Shows npx playwright test --headed and --debug, npx playwright show-trace, and screenshots.
Try: “This Playwright checkout test fails only in CI. Help me debug it.”
Runs code ·
Debugging failing testsConfig, page objects, fixtures, waiting, network mocking
Worked TypeScript examples for each of the five patterns.
Write ·
Playwright patterns (details.md)Custom commands and cy.intercept
Examples of a login command and request interception.
Write ·
Cypress patterns (details.md)Visual regression, sharding, accessibility with axe
Screenshot comparison, npx playwright test --shard=1/4 for CI, and an axe-core/playwright scan that needs npm install @axe-core/playwright.
Runs code ·
Advanced patterns (details.md)
From the official docs
Permissions
Low risk
The skill is guidance only, but your agent may write test files and run test commands in your project. Read each command before you approve it.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
Examples use test passwords
The worked examples contain sample credentials such as a test user's password. Replace them with test-only accounts and read secrets from environment variables.
It suggests installing a package
The accessibility example needs npm install @axe-core/playwright. Approve it only if you want that check.
Technical details
| Scopes |
|
|---|
Questions
What does the e2e-testing-patterns skill do?
It gives your agent a set of rules and worked examples for end-to-end tests with Playwright and Cypress. It helps most with writing new tests, fixing flaky ones and setting up CI.
How do I install it in Claude Code?
Use the install box at the top of this page. The wshobson/agents README also documents a skills-only route with npx skills add or gh skill install, and plugin routes for the whole collection.
Does it run tests for me?
It bundles no scripts. It teaches commands like npx playwright test and your agent runs them only through your normal approval prompts.
Playwright or Cypress?
It covers both. Most of its examples use Playwright, and Cypress gets a smaller section on custom commands and intercepts.
Is it safe?
It is plain instructions and example code, with no scripts. Your agent may write test files and run test commands in your project, and one example needs npm install @axe-core/playwright, so review commands before you approve them. Keep test passwords out of committed files.
What should I not test end to end?
SKILL.md's "What NOT to Test with E2E" list: unit-level logic (use unit tests), API contracts (use integration tests), edge cases (it says they are too slow) and internal implementation details.
Information
updated Nov 2, 2026
- Repository
- wshobson/agents
- Folder
plugins/developer-essentials/skills/e2e-testing-patterns
Sources
Docs, issue trackers and discussions this page is built from.
Show all 2Hide
- e2e-testing-patterns SKILL.md · github.com
- e2e-testing-patterns details.md · github.com