e2e-testing-patterns

Provide Playwright and Cypress patterns for end-to-end web testing.

6|2|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/amurata/cc-tools --skill e2e-testing-patterns-amurata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing-patterns
Source: https://github.com/amurata/cc-tools/tree/main/plugins/developer-essentials/skills/e2e-testing-patterns
Command: npx skills add https://github.com/amurata/cc-tools --skill e2e-testing-patterns-amurata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) and scripts (resource) components.

What problem does it solve?

This Skill helps developers build robust, maintainable, and efficient end-to-end (E2E) tests using Playwright and Cypress, reducing flaky tests and increasing confidence in deployments.

Core Features & Use Cases

  • Framework Guidance: Provides patterns for both Playwright and Cypress.
  • Best Practices: Covers setup, Page Object Model, fixtures, waiting strategies, network mocking, custom commands, and visual/accessibility testing.
  • Debugging Tips: Offers strategies for diagnosing and fixing failing tests.
  • Use Case: When starting a new project, use this Skill to establish E2E testing standards and implement effective test suites for critical user flows.

Quick Start

Use the e2e-testing-patterns skill to generate a Playwright Page Object Model for a login page.

Frequently Asked Questions about e2e-testing-patterns

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

FAQPage Schema
What are the best patterns to stop flaky E2E tests in Playwright and Cypress?

E2E testing patterns provide setup, data management, network mocking, and debugging strategies for Playwright and Cypress. Implementing these best practices reduces flaky tests and increases confidence in web application deployments.

How do I structure a Playwright E2E testing suite for maintainability?

Structure Playwright E2E testing suites using the Page Object Model, fixtures, and custom commands. Separating UI locators from test logic makes automated web application tests maintainable and easier to update.

Can I handle network mocking and fixtures in Cypress E2E tests?

Yes, E2E testing patterns provide best practices for network mocking and fixture management in Cypress. Intercepting network requests and isolating test data ensures reliable and deterministic execution of automated tests.

Does this cover visual regression and accessibility testing automation?

Yes, E2E testing patterns include guidance for integrating visual regression and accessibility checks into Playwright or Cypress suites. Verify both UI appearance and compliance during automated test execution.

Why do my Cypress E2E tests fail intermittently and how do I debug them?

Intermittent Cypress E2E test failures stem from timing issues or unmocked networks. Debug them using targeted diagnostic strategies, improving waiting strategies, and stabilizing the automated test suite.