What problem does it solve? Setting up a test framework from scratch involves dozens of decisions—framework selection, directory structure, fixtures, factories, configuration, and CI readiness—that are easy to get wrong and tedious to repeat across projects. ## Core Features & Use Cases - Automated Framework Selection: Detects the project stack (frontend, backend, fullstack, mobile) from project manifests and selects Playwright, Cypress, pytest, JUnit, Go test, xUnit, RSpec, or Maestro with documented rationale. - Complete Scaffolding: Creates test directory structures, framework config files, fixture architectures with mergeTests, faker-based data factories with auto-cleanup, sample tests, and environment files. - Validation & Resume: Supports Create, Resume, Validate, and Edit modes with a progress-tracking document and a comprehensive quality checklist. - Use Case: A developer starting a React project says "lets setup test framework" and receives a full Playwright setup with auth fixtures, sample E2E tests, package.json scripts, and a tests/README.md. ## Quick Start Ask the assistant to set up a test framework for this project, for example by saying "lets setup test framework".
