What problem does it solve? Setting up a production-grade test framework from scratch involves dozens of decisions—framework choice, directory layout, fixture architecture, data factories, CI reporters, and environment configuration—that teams often get wrong or leave inconsistent. ## Core Features & Use Cases - Stack-Aware Framework Selection: Auto-detects frontend, backend, fullstack, or mobile projects from manifests (package.json, pyproject.toml, go.mod, etc.) and selects Playwright, Cypress, pytest, JUnit, Go test, xUnit, RSpec, or Maestro accordingly. - Complete Scaffold Generation: Creates test directory structures, framework configs with tuned timeouts and reporters, .env templates, fixture indexes with mergeTests, faker-based data factories with auto-cleanup, and sample tests following Given-When-Then structure. - Tri-Modal Workflow: Supports Create, Resume (with progress frontmatter tracking), Validate (against a full checklist), and Edit modes, plus optional write-time enforcement hooks for Claude Code. - Use Case: A team starting a React + Vite storefront runs the workflow and receives a Playwright setup with merged fixtures, an auth fixture, an order factory, sample UI and API tests, package.json scripts, and a tests/README.md—validated against a quality checklist. ## Quick Start Ask the agent to set up a test framework for this project, for example by saying "let's setup test framework", and follow the Create mode prompts.
