What problem does it solve? Setting up a test framework from scratch involves dozens of decisions—directory structure, config files, fixtures, data factories, environment variables, and CI scripts—that are easy to get wrong and tedious to repeat across projects. ## Core Features & Use Cases - Guided Framework Initialization: Runs a step-by-step workflow that detects your stack (frontend, backend, or fullstack), selects Playwright, Cypress, pytest, JUnit, Go test, xUnit, or RSpec, and scaffolds the complete test directory structure. - Production Patterns Built In: Generates fixture architecture with mergeTests, Faker-based data factories with auto-cleanup, environment files, sample tests, and test documentation. - Validation & Resume Modes: Includes a validation checklist, resume support for interrupted runs, and edit mode for revising generated outputs. - Use Case: A developer starting a new Next.js project says "lets setup test framework" and receives a complete Playwright setup with config, fixtures, factories, sample E2E tests, and a tests/README.md. ## Quick Start Ask the assistant to set up a test framework for your project and it will detect your stack, choose the right framework, and scaffold the full test architecture.
