AI Plugin Index
e2e-testing-patterns
Skill by wshobson · updated · ★ 42k
Guides building end-to-end test suites with Playwright and Cypress. It is for developers who write E2E tests, debug flaky tests, or set testing standards. e2e-testing-patterns is published by wshobson on GitHub.
Install e2e-testing-patterns
Built from the published package, never by AIgit clone --depth 1 https://github.com/wshobson/agents /tmp/agents && mkdir -p ~/.claude/skills && cp -r /tmp/agents/plugins/developer-essentials/skills/e2e-testing-patterns ~/.claude/skills/e2e-testing-patternsRun in your terminal. Claude Code loads skills from ~/.claude/skills automatically.
git clone --depth 1 https://github.com/wshobson/agents /tmp/agents && mkdir -p ~/.gemini/antigravity-cli/skills && cp -r /tmp/agents/plugins/developer-essentials/skills/e2e-testing-patterns ~/.gemini/antigravity-cli/skills/e2e-testing-patternsAntigravity CLI loads skills from ~/.gemini/antigravity-cli/skills, or .agents/skills for one project.
Step-by-step: install e2e-testing-patterns in Antigravity CLI
Skills can run scripts on your machine. Some need an API key: check the README.
Last commit in the past day
MIT: permissive, fine for commercial use
Clear description, installs from GitHub, 41,623 stars, original repository
No risky patterns in the files we checked
About e2e-testing-patterns
This agent skill is a guide to end-to-end testing with Playwright and Cypress. It covers which user journeys to test end to end, which to leave to unit and integration tests, and how to follow the testing pyramid. It also lists best practices such as using data-testid attributes, avoiding brittle CSS selectors, using page objects, and keeping tests independent.
The skill includes code examples for stable selectors using Testing Library queries in Cypress and for debugging in Playwright. These cover headed and debug modes, the trace viewer, screenshots, test.step for clearer reports, and page.pause for inspecting page state. It is aimed at developers and QA engineers who need to build reliable, fast E2E suites, debug flaky tests, or set team standards for end-to-end testing.
Written from the project's SKILL.md and checked against it.
What e2e-testing-patterns can do
- Test scope guidanceExplains which critical user journeys to test end to end and which to leave to unit or integration tests.
- Selector best practicesRecommends data-testid or data-cy attributes and Testing Library role and label queries over CSS selectors.
- Playwright debuggingShows headed mode, debug mode, trace viewer use, and screenshots for diagnosing failing tests.
- Test stepsShows how to group checkout steps with test.step for clearer test reports.
- Flaky test guidanceAdvises proper waits instead of fixed timeouts and tests that stay independent and deterministic.
- Common pitfallsLists frequent E2E mistakes such as slow tests, coupled tests, and missing test data cleanup.
What you need
- Playwright
- Cypress
- @testing-library/cypress for findBy* commands
Weekly newsletter
Like e2e-testing-patterns? Get the best new skills every week
The best new tools, security warnings before you install something risky, and one practical tip. Free, three minute read.
Try asking
- Write a Playwright E2E test for the login flow using stable selectors
- Help me debug a flaky Cypress test that uses fixed timeouts
- Review my E2E checkout test and suggest test.step grouping
Good to know
- Detailed patterns are in references/details.md, which is not included in this source
- The findBy* examples need the @testing-library/cypress package
Security check
ANo download-and-run commands, hidden instructions or signs of sending keys out were found.
Checked automatically: plugins/developer-essentials/skills/e2e-testing-patterns/SKILL.md. This looks for known risky patterns and is not a full audit. How grades work
Inside the skill
-
SKILL.md4 KB -
references/details.md10 KB
Alternatives to e2e-testing-patterns
All alternatives →
7-stage super workflow for GitHub repo audit, cleanup, PR review, and competitor analysis
Build Gradio web UIs and demos in Python. Use when creating, modifying, debugging, or answering questions about Gradio and its capabilties, components, event listeners, or layouts.
Writes the launch for an app clone: the landing page built on the positioning angle, pricing set against the original's public pricing and its users' complaints, and the App Store and Google Play listing linted against the stores' limits and copycat rules. Use when the user says "landing page", "pricing", "how much should I charge", "App Store listing", "store screenshots", "launch plan", "Product Hunt", or after /replica-brand.
Adds a self-hosted "Stargazers over time" chart to a GitHub repo's README. It generates a static SVG and refreshes it weekly with a GitHub Action. Useful when a third-party star chart shows "Requires authentication".
Creates production-ready FastAPI project structures with async patterns, dependency injection, and error handling. It is for developers starting new FastAPI applications or backend API projects.
Splits a large pull request into smaller PRs so each one needs fewer CODEOWNERS reviewer groups. It is written for contributors to NVIDIA's Megatron-LM repository.
e2e-testing-patterns: common questions
When should I use E2E tests instead of unit tests?
The skill says to use E2E tests for critical user journeys, complex interactions, cross-browser checks, real API integration, and authentication flows. Unit-level logic, API contracts, and edge cases should be tested with other test types.
Which selectors does this skill recommend?
It recommends data-testid or data-cy attributes and Testing Library queries such as findByRole and findByLabelText. It advises against CSS classes, DOM structure, and nth-child selectors.
How do I debug a failing Playwright test with this skill?
The skill shows running tests in headed mode or debug mode, recording traces with trace: 'on-first-retry', viewing them with show-trace, taking screenshots, and using page.pause to inspect the page.
How do I install e2e-testing-patterns?
Run the command above to copy the skill into ~/.claude/skills/. Claude Code picks it up automatically.
Is e2e-testing-patterns free?
The code is published under the MIT licence. The service it connects to may have its own pricing.
Is e2e-testing-patterns safe to use?
It scores 94 of 100. Grades: maintenance A, licence A, quality A. Security check: grade A, no risky patterns found in the files checked. Review the code before you install. How grades work.
What are alternatives to e2e-testing-patterns?
Similar skills: openclaw-github-repo-commander, gradio, replica-launch, star-history-chart.