e2e-testinglisted

Use when designing end-to-end test suites, visual regression testing, or cross-browser test strategies. Covers Playwright/Cypress test architecture, page object patterns, test data management, visual snapshot comparison, cross-browser matrix, and CI integration. Do not use for unit/integration test strategy (use testing-strategy) or code pattern audit (use pattern-analysis).
dtsong/agentic-council · ★ 0 · Testing & QA · score 78

Install: claude install-skill dtsong/agentic-council

# E2E Testing ## Purpose Design end-to-end test suites that validate critical user journeys across the full stack, catch visual regressions, and ensure cross-browser compatibility with efficient CI execution. ## Scope Constraints Analyzes application architecture and existing test infrastructure to design E2E test strategy. Does not execute tests or modify application code. Does not set up CI pipelines (hand off to operator/deployment-plan). ## Inputs - Application type and tech stack (SPA, SSR, mobile web) - Critical user journeys to cover - Current E2E framework in use, if any (Playwright, Cypress, Selenium) - CI environment constraints (runner OS, parallelism, time budget) - Browser/device matrix requirements ## Input Sanitization No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets. ## Procedure ### Progress Checklist - [ ] Step 1: Define test scope and critical paths - [ ] Step 2: Design test architecture - [ ] Step 3: Plan visual regression strategy - [ ] Step 4: Configure cross-browser matrix - [ ] Step 5: Design test data management - [ ] Step 6: Plan CI integration ### Step 1: Define Test Scope and Critical Paths - Identify critical user journeys (auth, core workflows, payment, onboarding). - Prioritize by business impact and failure cost. - Define smoke test subset for deploy gates (target <2 min). - Map which journeys need full E2E vs can rely on integration tests. - Set coverage target: aim fo