e2e-testing-patterns

Build reliable end-to-end test suites with Playwright and Cypress.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gleeb/ai-registry --skill e2e-testing-patterns-gleeb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-testing-patterns
Source: https://github.com/gleeb/ai-registry/tree/main/common-skills/e2e-testing-patterns
Command: npx skills add https://github.com/gleeb/ai-registry --skill e2e-testing-patterns-gleeb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you build and maintain end-to-end (E2E) test suites that catch real regressions without becoming flaky, slow, or overly tied to implementation details.

Core Features & Use Cases

  • E2E testing strategy: Use E2E for critical user journeys and cross-browser coverage, while avoiding slow or redundant testing that belongs in unit or integration layers.
  • Playwright patterns: Set up robust configuration, use Page Object Model for maintainable test code, apply deterministic fixtures, and choose reliable waiting strategies.
  • Flake reduction & debugging: Prefer condition-based waits and meaningful assertions, mock/intercept network calls when needed, and use tracing/video/screenshots plus step-level reporting to diagnose failures.
  • Cypress patterns: Create custom commands for reuse, intercept/mock APIs for deterministic runs, and simulate slow networks to validate resilience.
  • Advanced E2E quality checks: Add visual regression and accessibility checks to ensure UI correctness and inclusive user experiences.

Quick Start

Use the e2e-testing-patterns skill to design E2E tests for a critical user workflow using Playwright and add stable selectors and deterministic waiting so the suite runs fast and reliably.

Frequently Asked Questions about e2e-testing-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix flaky Playwright tests?▼

Fix flaky Playwright tests by replacing arbitrary timeouts with condition-based waits, using robust selectors, intercepting network calls, and ensuring deterministic data cleanup for stable execution.

What is the best way to mock network requests in Cypress?▼

Mock network requests in Cypress by using the intercept command to stub API responses, ensuring deterministic test runs and allowing you to simulate slow networks to validate application resilience.

How do you structure an E2E testing strategy?▼

Structure an E2E testing strategy by targeting critical user journeys and cross-browser coverage, while avoiding slow or redundant tests that belong in unit or integration layers.

Can I add accessibility testing to my E2E automation suite?▼

Yes, you can add accessibility testing to your E2E automation suite by integrating visual regression and accessibility checks to ensure UI correctness and inclusive user experiences.

How do I debug failing end-to-end tests?▼

Debug failing end-to-end tests by utilizing tracing, video recordings, screenshots, and step-level reporting to accurately diagnose failures and analyze test execution behavior.

Playwright vs Cypress: which should I use for E2E testing?▼

Choose Playwright for robust configuration and cross-browser parallelization, or Cypress for custom commands and API mocking; both stabilize E2E tests but offer different configuration patterns.