e2e-testing-patterns

Implements end-to-end test suites with stable selectors, retries, and CI parallelization.

1|Updated Jul 20, 2026
One-click install
npx skills add https://github.com/gonzoblasco/ai-developer-stack --skill e2e-testing-patterns-gonzoblasco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-testing-patterns
Source: https://github.com/gonzoblasco/ai-developer-stack/tree/main/tools-automation/e2e-testing-patterns
Command: npx skills add https://github.com/gonzoblasco/ai-developer-stack --skill e2e-testing-patterns-gonzoblasco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? End-to-end tests often become flaky, slow, and hard to maintain, causing teams to lose trust in their test suites and ship regressions to users. This Skill provides structured patterns for building E2E tests that catch real issues without constant maintenance overhead. ## Core Features & Use Cases - Critical Journey Coverage: Identify and test the user workflows that matter most, with stable selectors and dedicated test data strategies. - Flakiness Reduction: Apply retries, tracing, and test isolation to debug and stabilize unreliable tests. - CI/CD Integration: Run tests in parallel pipelines with artifact capture, multi-browser coverage, and accessibility validation. - Use Case: A team preparing a release pipeline uses this Skill to define E2E coverage for login, checkout, and account settings, then wires the tests into CI with screenshots and traces captured on failure. ## Quick Start Ask the AI to design an end-to-end test plan for your app's critical user journeys with stable selectors and CI parallelization.

Frequently Asked Questions about e2e-testing-patterns

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

FAQPage Schema
How do I write end-to-end tests that are not flaky?▼

Flaky E2E tests are reduced by using stable selectors instead of brittle CSS paths, isolating tests with dedicated data, and adding retries with tracing. Capturing artifacts like screenshots and traces on failure makes intermittent issues diagnosable.

How to set up E2E tests in a CI/CD pipeline?▼

Run E2E tests in CI with parallelization to keep execution time low and capture artifacts such as traces and screenshots for failed runs. Use dedicated test accounts and data so pipelines do not depend on production state.

What should I test with end-to-end tests versus unit tests?▼

E2E tests should cover critical user journeys like signup, checkout, and core workflows where multiple systems interact. Unit and integration tests are better for isolated logic, so do not duplicate that coverage at the E2E level.

Can E2E tests validate accessibility requirements?▼

Yes, E2E suites can include accessibility checks as part of critical journey validation, catching issues like missing labels or keyboard navigation failures. This complements, but does not replace, dedicated accessibility audits.

When should I not use end-to-end testing?▼

Avoid E2E testing when unit or integration tests suffice, when the environment cannot support stable UI automation, or when you cannot provision safe test accounts and data. Never run destructive tests against production systems.