End-to-end tests often become slow, brittle, and hard to trust. This skill provides Playwright and Cypress patterns for stable workflows, selectors, data setup, mocking, and debugging.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "e2e-testing-patterns" from https://skillstore.io/skills/wshobson-e2e-testing-patterns.md and its manifest at https://skillstore.io/api/skills/wshobson-e2e-testing-patterns/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Static findings were reviewed against SKILL.md and appear to be false positives from Markdown fences, TypeScript examples, local test URLs, and standard CI variables. No prompt injection, data exfiltration intent, unauthorized external command execution, or malicious network behavior was found.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Design Playwright or Cypress tests for login, checkout, profile, signup, and other critical browser workflows.
Reduce Test Flakiness
Replace fixed waits and brittle selectors with condition-based waits, stable attributes, fixtures, and focused assertions.
Standardize Test Practices
Define team patterns for page objects, data setup, network mocking, sharding, accessibility checks, and debugging.
Try These Prompts
Plan E2E Coverage
Use the e2e-testing-patterns skill to identify the critical user journeys for this feature and propose focused Playwright or Cypress tests.
Write Stable Tests
Use the e2e-testing-patterns skill to write an E2E test for this workflow with stable selectors, clear assertions, and safe test data cleanup.
Debug Flaky Tests
Use the e2e-testing-patterns skill to review this flaky E2E test and recommend better waits, selectors, fixtures, and debugging steps.
Design A Test Strategy
Use the e2e-testing-patterns skill to design an E2E testing strategy with page objects, fixtures, mocks, sharding, visual checks, and accessibility checks.
Best Practices
Test user-visible behavior and critical journeys before adding broad E2E coverage.
Use stable selectors, isolated data, and condition-based waits to reduce flakiness.
Capture traces, screenshots, videos, and clear test steps for faster debugging.
Avoid
Using fixed timeouts instead of waiting for meaningful page or network conditions.
Relying on CSS classes, DOM nesting, or nth-child selectors for important flows.
Testing every edge case with E2E tests when unit or integration tests are better.
Frequently Asked Questions
Which frameworks does this skill cover?
It covers Playwright and Cypress patterns for configuration, selectors, data setup, mocking, accessibility, and debugging.
Can it generate complete runnable tests?
It can guide test design and examples, but users must adapt routes, selectors, fixtures, and dependencies to their project.
Does it help with flaky tests?
Yes. It recommends condition-based waits, stable selectors, isolated data, traces, screenshots, and focused assertions.
Does it replace other test types?
No. It explains that unit, integration, and API contract tests should cover lower-level logic and contracts.
Is it suitable for CI pipelines?
Yes. It includes retry, worker, reporter, sharding, screenshot, video, and trace guidance for CI test suites.
Does it include security testing guidance?
It focuses on E2E reliability and accessibility. Security-specific testing requires separate threat modeling and tools.