Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
wshobson avatar

E2e Testing Patterns

  • 20k installs
  • 38.3k repo stars
  • Updated July 22, 2026
  • wshobson/agents

e2e-testing-patterns is an agent skill that Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when im.

About

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs improve confidence and enable fast deployment Use when implementing E2E tests debugging flaky tests or establishing testing standards name e2e-testing-patterns description Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs improve confidence and enable fast deployment Use when implementing E2E tests debugging flaky tests or establishing testing standards E2E Testing Patterns Build reliable fast and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do When to Use This Skill Implementing end-to-end test automation Debugging flaky or unreliable tests Testing critical user workflows Setting up CI CD test pipelines Testing across multiple browsers Validating accessibility requirements Testing responsive designs Establishing E2E testing standards Core Concepts 1 E2E Testing Fundamentals What to Test with E2E Critical user journeys login checkout signup Complex interactions drag-and-drop multi-step forms Cross-browser compatibility Real API integration Authentication flows Wha.

  • Implementing end-to-end test automation
  • Debugging flaky or unreliable tests
  • Testing critical user workflows
  • Setting up CI/CD test pipelines
  • Testing across multiple browsers

E2e Testing Patterns by the numbers

  • 20,004 all-time installs (skills.sh)
  • +376 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #30 of 2,184 Testing & QA skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

e2e-testing-patterns capabilities & compatibility

Capabilities
implementing end to end test automation · debugging flaky or unreliable tests · testing critical user workflows · setting up ci/cd test pipelines · testing across multiple browsers
Use cases
documentation
From the docs

What e2e-testing-patterns says it does

--- name: e2e-testing-patterns description: Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment.
SKILL.md
Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
SKILL.md
--- # E2E Testing Patterns Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do.
SKILL.md
Read that file when the navigation tier above is insufficient.
SKILL.md
npx skills add https://github.com/wshobson/agents --skill e2e-testing-patterns

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs20k
repo stars38.3k
Security audit3 / 3 scanners passed
Last updatedJuly 22, 2026
Repositorywshobson/agents

What problem does e2e-testing-patterns solve for developers using this skill?

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky te

Who is it for?

Developers who need e2e-testing-patterns patterns described in the cached skill documentation.

Skip if: Skip when docs are empty or the task is outside the skill's documented scope.

When should I use this skill?

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky te

What you get

Actionable workflows and conventions from SKILL.md for e2e-testing-patterns.

  • playwright.config.ts
  • page object files
  • CI test reports

By the numbers

  • Documents CI retries set to 2 with 30000 ms test timeout and 5000 ms expect timeout

Files

SKILL.mdMarkdownGitHub ↗

E2E Testing Patterns

Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do.

When to Use This Skill

  • Implementing end-to-end test automation
  • Debugging flaky or unreliable tests
  • Testing critical user workflows
  • Setting up CI/CD test pipelines
  • Testing across multiple browsers
  • Validating accessibility requirements
  • Testing responsive designs
  • Establishing E2E testing standards

Core Concepts

1. E2E Testing Fundamentals

What to Test with E2E:

  • Critical user journeys (login, checkout, signup)
  • Complex interactions (drag-and-drop, multi-step forms)
  • Cross-browser compatibility
  • Real API integration
  • Authentication flows

What NOT to Test with E2E:

  • Unit-level logic (use unit tests)
  • API contracts (use integration tests)
  • Edge cases (too slow)
  • Internal implementation details

2. Test Philosophy

The Testing Pyramid:

        /\
       /E2E\         ← Few, focused on critical paths
      /─────\
     /Integr\        ← More, test component interactions
    /────────\
   /Unit Tests\      ← Many, fast, isolated
  /────────────\

Best Practices:

  • Test user behavior, not implementation
  • Keep tests independent
  • Make tests deterministic
  • Optimize for speed
  • Use data-testid, not CSS selectors

Detailed patterns and worked examples

Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.

Best Practices

1. Use Data Attributes: data-testid or data-cy for stable selectors 2. Avoid Brittle Selectors: Don't rely on CSS classes or DOM structure 3. Test User Behavior: Click, type, see - not implementation details 4. Keep Tests Independent: Each test should run in isolation 5. Clean Up Test Data: Create and destroy test data in each test 6. Use Page Objects: Encapsulate page logic 7. Meaningful Assertions: Check actual user-visible behavior 8. Optimize for Speed: Mock when possible, parallel execution

// ❌ Bad selectors
cy.get(".btn.btn-primary.submit-button").click();
cy.get("div > form > div:nth-child(2) > input").type("text");

// ✅ Good selectors
cy.getByRole("button", { name: "Submit" }).click();
cy.getByLabel("Email address").type("user@example.com");
cy.get('[data-testid="email-input"]').type("user@example.com");

Common Pitfalls

  • Flaky Tests: Use proper waits, not fixed timeouts
  • Slow Tests: Mock external APIs, use parallel execution
  • Over-Testing: Don't test every edge case with E2E
  • Coupled Tests: Tests should not depend on each other
  • Poor Selectors: Avoid CSS classes and nth-child
  • No Cleanup: Clean up test data after each test
  • Testing Implementation: Test user behavior, not internals

Debugging Failing Tests

// Playwright debugging
// 1. Run in headed mode
npx playwright test --headed

// 2. Run in debug mode
npx playwright test --debug

// 3. Use trace viewer
await page.screenshot({ path: 'screenshot.png' });
await page.video()?.saveAs('video.webm');

// 4. Add test.step for better reporting
test('checkout flow', async ({ page }) => {
    await test.step('Add item to cart', async () => {
        await page.goto('/products');
        await page.getByRole('button', { name: 'Add to Cart' }).click();
    });

    await test.step('Proceed to checkout', async () => {
        await page.goto('/cart');
        await page.getByRole('button', { name: 'Checkout' }).click();
    });
});

// 5. Inspect page state
await page.pause();  // Pauses execution, opens inspector

Related skills

How it compares

Use e2e-testing-patterns for Playwright-specific reliability recipes; reach for unit or API test skills when browser automation is not required.

FAQ

What does e2e-testing-patterns do?

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing

When should I use e2e-testing-patterns?

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing

Is e2e-testing-patterns safe to install?

Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.