mcpField
E
e2e-testing-patterns

e2e-testing-patterns

github.com/rmyndharisTesting & quality1.9k43 installsUpdated 2w ago
Repository

About e2e-testing-patterns

A skill for teams building end-to-end test automation, with guidance on reliable test design, flaky-test debugging, critical user journeys, CI, and cross-browser validation.

Key features

  1. 01Identify critical journeys and success criteria
  2. 02Plan stable selectors and test data
  3. 03Use retries, tracing, and isolation
  4. 04Parallelize CI runs and capture artifacts
  5. 05Validate accessibility and responsive designs

Use cases

  1. 01Debug flaky end-to-end tests
  2. 02Cover critical user workflows
  3. 03Run tests in CI/CD pipelines
  4. 04Establish end-to-end testing standards

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rmyndharis/antigravity-skills --skill e2e-testing-patterns

After installing, type/e2e-testing-patternsin Claude Code to confirm it loaded.

Bundled filesresources/implementation-playbook.md

Details

From the project README

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.

Use this skill when

  • 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

Do not use this skill when

  • You only need unit or integration tests
  • The environment cannot support stable UI automation
  • You cannot provision safe test accounts or data

Instructions

  1. Identify critical user journeys and success criteria.
  2. Build stable selectors and test data strategies.
  3. Implement tests with retries, tracing, and isolation.
  4. Run in CI with parallelization and artifact capture.

Safety

  • Avoid running destructive tests against production.
  • Use dedicated test data and scrub sensitive output.

Resources

  • resources/implementation-playbook.md for detailed E2E patterns and templates.

Comments

Markdown supported