# Build Reliable End-to-End Test Suites

End-to-end tests often become slow, flaky, and difficult to maintain. This skill provides Playwright and Cypress patterns for stable workflows, test data, CI, debugging, and accessibility.

## Install

```bash
npx skillstore add sickn33/e2e-testing-patterns
```

## Metadata

- Status: approved
- Slug: sickn33-e2e-testing-patterns
- Skillstore revision: r2
- Version status: missing
- Tree hash: f3ac4b1a3cf15178e6288578704ab5fff76f609dd6bb11347bae2674a8b78aa1
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/e2e-testing-patterns
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/sickn33-e2e-testing-patterns
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-e2e-testing-patterns/manifest

## Capabilities

- Plan focused E2E coverage for critical user journeys and success criteria.
- Create Playwright configurations, page objects, fixtures, waiting strategies, network mocks, and browser projects.
- Create Cypress configurations, custom commands, request helpers, intercepts, and stable selectors.
- Structure isolated test data setup and cleanup with environment-based credentials.
- Add visual regression, accessibility, sharding, tracing, screenshots, and video workflows.
- Diagnose flaky tests using deterministic waits, user-visible assertions, traces, headed runs, and debug mode.

## Use Cases

- Stabilize regression suites: Replace fixed waits and brittle selectors with deterministic conditions, isolated fixtures, and user-visible assertions.
- Cover critical product journeys: Design maintainable browser tests for authentication, checkout, profile updates, responsive interfaces, and accessibility.
- Scale browser tests in CI: Configure retries, browser projects, sharding, traces, screenshots, videos, and structured reports for continuous delivery.

## Prompt Templates

### Plan a critical journey

```
Review [workflow] for [application]. Define the critical path, required test data, stable selectors, success criteria, and cleanup steps.
```

### Design a Playwright suite

```
Design a Playwright E2E suite for [feature]. Include page objects, fixtures, deterministic waits, browser coverage, failure artifacts, and accessibility checks.
```

### Refactor flaky Cypress tests

```
Analyze these Cypress test symptoms: [details]. Identify likely causes and propose stable selectors, intercepts, assertions, test isolation, and debugging steps.
```

### Architect CI browser coverage

```
Create an E2E strategy for [system] and [CI platform]. Balance sharding, retries, real integrations, mocks, visual checks, artifacts, security, and runtime.
```

## Limitations

- Provides patterns and examples; it does not execute tests or verify application-specific behavior.
- Requires the target application, test accounts, routes, selectors, and expected outcomes.
- Covers Playwright and Cypress patterns, not full framework installation or infrastructure provisioning.
- Referenced auxiliary files in the playbook are not included in this package.

## Best Practices

- Test user-visible behavior and reserve E2E coverage for critical journeys.
- Use stable role, label, or data-attribute selectors with deterministic waits.
- Create isolated test data, clean it after each test, and protect credentials in CI.

## Anti Patterns

- Do not use fixed delays when the test can wait for a specific state or response.
- Do not couple test order or reuse mutable data across independent scenarios.
- Do not run destructive test flows against production systems or real customer data.

## Security Audit

- Audited at: 2026-07-23T23:13:33.237\+00:00
- Summary: All 23 static alerts are false positives caused by Markdown, TypeScript syntax, standard test configuration, and expected local test traffic. The files contain documentation and code samples, with no executable scripts, prompt injection, credential exfiltration, or malicious intent. Environment-based administrator credentials should remain limited to isolated test accounts and protected CI secrets.

## Stats

- Views: 156
- Downloads: 15
- Favorites: 1
- Popularity score: 0