Xpersona
E

E2E Testing Patterns

CLAWHUB · Unverified

Build reliable, fast E2E test suites with Playwright and Cypress. Critical user journey coverage, flaky test elimination, CI/CD integration. Skill: E2E Testing Patterns Owner: wpank Summary: Build reliable, fast E2E test suites with Playwright and Cypress. Critical user journey coverage, flaky test elimination, CI/CD integration. Tags: latest:1.0.0 Version history: v1.0.0 | 2026-02-10T13:24:57.262Z | user Initial release — best-practice patterns for building bulletproof end-to-end test suites with Playwright and Cypress. - Provides guidance and example co

62
Rank
84
Safety
14k
Downloads

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 13.7K downloads reported by the source. Last updated 11/16/2026.

Avoid when

  • Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Install and run

Setup complexity: low.

clawhub skill install s17bjjbnm7xjckd29e1h2641ks8849md:e2e-testing-patterns
  1. Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
  2. Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-wpank-e2e-testing-patterns-patterns-2/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

19,140 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: e2e-testing-patterns
model: standard
category: testing
description: Build reliable, fast E2E test suites with Playwright and Cypress. Critical user journey coverage, flaky test elimination, CI/CD integration.
version: 1.0
keywords: [e2e, end-to-end, playwright, cypress, browser testing, integration tests, test automation, flaky tests, visual regression]
---

# E2E Testing Patterns

> Test what users do, not how code works. E2E tests prove the system works as a whole — they're your confidence to ship.


## Installation

### OpenClaw / Moltbot / Clawbot

```bash
npx clawhub@latest install e2e-testing-patterns
```


---

## WHAT This Skill Does

Provides patterns for building end-to-end test suites that:
- Catch regressions before users do
- Run fast enough for CI/CD
- Remain stable (no flaky failures)
- Cover critical user journeys without over-testing

## WHEN To Use

- **Implementing E2E test automation** for a web application
- **Debugging flaky tests** that fail intermittently
- **Setting up CI/CD test pipelines** with browser tests
- **Testing critical user workflows** (auth, checkout, signup)
- **Choosing what to test with E2E** vs unit/integration tests

---

## Test Pyramid — Know Your Layer

```
        /\
       /E2E\         ← FEW: Critical paths only (this skill)
      /─────\
     /Integr\        ← MORE: Component interactions, API contracts
    /────────\
   /Unit Tests\      ← MANY: Fast, isolated, cover edge cases
  /────────────\
```

### What E2E Tests Are For

| E2E Tests ✓ | NOT E2E Tests ✗ |
|-------------|-----------------|
| Critical user journeys (login → dashboard → action → logout) | Unit-level logic (use unit tests) |
| Multi-step flows (checkout, onboarding wizard) | API contracts (use integration tests) |
| Cross-browser compatibility | Edge cases (too slow, use unit tests) |
| Real API integration | Internal implementation details |
| Authentication flows | Component visual states (use Storybook) |

**Rule of thumb:** If it would devastate your business to break, E2E test it. If it's just inconvenient, test it faster with unit/integration tests.

---

## Core Principles

| Principle | Why | How |
|-----------|-----|-----|
| **Test behavior, not implementation** | Survives refactors | Assert on user-visible outcomes, not DOM structure |
| **Independent tests** | Parallelizable, debuggable | Each test creates its own data, cleans up after |
| **Deterministic waits** | No flakiness | Wait for conditions, not fixed timeouts |
| **Stable selectors** | Survives UI changes | Use `data-testid`, roles, labels — never CSS classes |
| **Fast feedback** | Developers run them | Mock external services, parallelize, shard |

---

## Playwright Patterns

### Configuration

```typescript
// playwright.config.ts
import { defineConfig, devices } from "@playwright/test";

export default defineConfig({
  testDir: "./e2e",
  timeout: 30000,
  expect: { timeout: 5000 },
  fullyParallel: true,
  forbidOnly: !!process.env.CI,
  retri

README.md

# E2E Testing Patterns

Build reliable, fast end-to-end test suites with Playwright and Cypress. Critical user journey coverage, flaky test elimination, and CI/CD integration.

## What's Inside

- Test pyramid guidance (what E2E tests are for vs. not for)
- Core principles (behavior over implementation, independent tests, deterministic waits, stable selectors)
- Playwright patterns (config, Page Object Model, fixtures, smart waiting, network mocking)
- Cypress patterns (custom commands, network intercepts)
- Selector strategy with priority ranking (roles → labels → data-testid → text)
- Visual regression testing
- Accessibility testing with axe-core
- Debugging failed tests (headed mode, trace viewer, test steps)
- Flaky test diagnosis checklist
- CI/CD integration with GitHub Actions

## When to Use

- Implementing E2E test automation for a web application
- Debugging flaky tests that fail intermittently
- Setting up CI/CD test pipelines with browser tests
- Testing critical user workflows (auth, checkout, signup)
- Choosing what to test with E2E vs unit/integration tests

## Installation

```bash
npx add https://github.com/wpank/ai/tree/main/skills/testing/e2e-testing-patterns
```

### OpenClaw / Moltbot / Clawbot

```bash
npx clawhub@latest install e2e-testing-patterns
```

### Manual Installation

#### Cursor (per-project)

From your project root:

```bash
mkdir -p .cursor/skills
cp -r ~/.ai-skills/skills/testing/e2e-testing-patterns .cursor/skills/e2e-testing-patterns
```

#### Cursor (global)

```bash
mkdir -p ~/.cursor/skills
cp -r ~/.ai-skills/skills/testing/e2e-testing-patterns ~/.cursor/skills/e2e-testing-patterns
```

#### Claude Code (per-project)

From your project root:

```bash
mkdir -p .claude/skills
cp -r ~/.ai-skills/skills/testing/e2e-testing-patterns .claude/skills/e2e-testing-patterns
```

#### Claude Code (global)

```bash
mkdir -p ~/.claude/skills
cp -r ~/.ai-skills/skills/testing/e2e-testing-patterns ~/.claude/skills/e2e-testing-patterns
```

## Related Skills

- [testing-patterns](../testing-patterns/) — Unit and integration testing patterns
- [testing-workflow](../testing-workflow/) — Orchestrates E2E testing within the full testing strategy
- [quality-gates](../quality-gates/) — CI/CD quality checkpoints including E2E gates

---

Part of the [Testing](..) skill category.

_meta.json

{
  "ownerId": "kn77z49xfssappp65hpybb9gx180x56e",
  "slug": "e2e-testing-patterns",
  "version": "1.0.0",
  "publishedAt": 1770729897262
}

skill-card.md

## Description:

Build reliable, fast E2E test suites with Playwright and Cypress, with guidance for critical user journey coverage, flaky test elimination, and CI/CD integration.

This skill is ready for commercial/non-commercial use.

## Publisher:

[wpank](https://clawhub.ai/user/wpank)

### License/Terms of Use:


## Use Case:

Developers and engineers use this skill to design, implement, debug, and maintain end-to-end test automation for web applications using Playwright and Cypress. It is especially relevant for critical workflows, flaky test diagnosis, browser-test CI/CD pipelines, selector strategy, accessibility checks, and visual regression testing.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: Mutable npx install commands can fetch changing packages or code in sensitive environments.

Mitigation: Prefer a pinned or reviewed ClawHub release before installation, and keep Playwright and related tools as pinned dev dependencies with a lockfile in project and CI environments.

## Reference(s):

- [ClawHub skill page](https://clawhub.ai/wpank/skills/e2e-testing-patterns)
- [Artifact README](artifact/README.md)
- [Artifact skill definition](artifact/SKILL.md)

## Skill Output:

**Output Type(s):** [Text, Markdown, Code, Shell commands, Configuration, Guidance]

**Output Format:** [Markdown guidance with TypeScript, YAML, and bash examples]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Includes Playwright, Cypress, accessibility, visual regression, debugging, and CI/CD testing patterns.]

## Skill Version(s):

1.0.0 (source: server release metadata and skill frontmatter)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Sponsored

Ads related to E2E Testing Patterns and adjacent AI workflows.