e2e-testing-patterns

Fix flaky E2E tests by implementing proper waiting strategies and network mocking. This Skill provides proven patterns for both Playwright and Cypress to handle asynchronous operations, stabilize selectors, and eliminate timing-related test failures.

Use the Page Object Model to encapsulate UI elements and interactions into reusable classes. This Skill provides implementation examples for Playwright and Cypress, separating test logic from locators to enhance maintainability and reduce duplication across test suites.

Yes, it supports both frameworks. The Skill provides framework-agnostic patterns and specific code examples for implementing E2E tests, covering setup, custom commands, fixtures, and visual regression testing for both Playwright and Cypress environments.

Network mocking intercepts API requests to return controlled responses, isolating tests from backend dependencies. Use it to simulate error states, edge cases, or specific data scenarios, which this Skill covers to ensure deterministic and fast test execution.

Implement visual regression testing by capturing baseline screenshots and comparing them against future runs. This Skill covers the setup and configuration needed to detect unintended UI changes and catch visual regressions before deployment.

E2E test suites fail in parallel execution due to shared state or resource conflicts. This Skill addresses this by providing patterns for test sharding, proper fixture management, and isolated test contexts to enable fast and reliable parallel runs.