What problem does it solve?
Ensures feature implementations are validated with thorough, repeatable tests and prevents incomplete or visually broken releases by enforcing planning, execution, and verification across unit, integration, and browser E2E tests. It also mitigates AI context overflow during browser-driven E2E runs by prescribing session limits and data-minimizing rules.
Core Features & Use Cases
- Pre-implementation Test Plans: Create initial state, interaction, transition, edge case, integration, and responsive breakpoint tests before coding starts.
- E2E Context Management: Rules for one suite per session, max three screenshots, prefer evaluate_script() over large snapshots, and reloads between major flows to avoid context exhaustion.
- Coverage & Validation Gates: Enforces minimum coverage for new code, mandatory responsive breakpoint checks, and documented post-implementation browser test results.
- Use Case: Use when implementing a new UI feature to generate a detailed test plan, run targeted E2E checks in the browser, and record verification artifacts for release gates.
Quick Start
Use the testing-workflow skill to produce a pre-implementation test plan, required coverage thresholds, and a browser E2E checklist for the new feature.