e2e-testinglisted

Playwright E2E testing patterns — Page Object Model, configuration, CI/CD integration, artifact management, flaky test strategies, PLUS the decision-time patterns that come before the first test is written (black-box helper scripts, static-vs-dynamic routing, multi-server orchestration, reconnaissance-then-action, networkidle discipline).
Nmor/the-claude-council · ★ 9 · Testing & QA · score 66

Install: claude install-skill Nmor/the-claude-council

# E2E Testing Patterns Comprehensive Playwright patterns for building stable, fast, and maintainable E2E test suites. ## Purpose End-to-end tests verify the system as a user encounters it — across the full HTTP stack, real browser engine, real DOM, real network round-trips to (mocked or real) backends. This skill captures the decision-time patterns + execution patterns + flake-management patterns that separate "we have e2e tests" from "our e2e suite catches real regressions without burning the on-call rotation". What this skill does NOT cover: - Unit tests + component tests (sister `tdd-workflow` skill; framework-specific helpers in `vue3-patterns`, `frontend-patterns`). - API-only contract tests (sister `api-design` skill; `contract-testing.md` rule). - Accessibility audits (sister `wcag-accessibility` skill — axe-core in CI is a different gate). - Visual regression (separate tooling — Chromatic / Percy / Argos). - Load + performance testing (k6 / Gatling / Locust — different category). ## When to use - Adding a critical user journey (signup, checkout, payment, deletion-of-account, plan-tier upgrade). - Verifying cross-system interactions (web ↔ API ↔ worker ↔ DB) that unit tests cannot reach. - Reproducing a production bug whose surface is "user clicked X then Y broke" (the report shape that calls for browser-level repro). - Establishing the smoke-test suite that gates every production deploy. ## When NOT to use - The target is pure backend HTTP — use `supertest` /