tdd-test-setup

TDD test infrastructure setup analyzes your architecture documentation to recommend a tailored test runner, directory layout, and starter test. It aligns testing choices with detected language frameworks and existing project constraints rather than relying on guesses.

Before configuring a TDD test runner, you need completed architecture documentation describing key components. The setup process reads docs/architecture.md and docs/vision.md to tailor test tooling, directory layout, and coverage to your specific project constraints.

Architecture-aware test setup improves testing workflows by reading architecture signals to recommend deterministic test tooling and a starter test. This ensures the test infrastructure directly reflects your documented components instead of using generic boilerplate configurations.

Yes, test infrastructure setup outlines concrete steps to integrate with Claude Code permissions, CI workflows, and gitignore rules. This guided configuration manages session artifacts and ensures the test runner operates within your established development environment.

The best way to wire a starter test is to follow architecture-driven recommendations that specify a concrete test runner and directory layout. This deterministic wiring provides an executable starter test demonstrating how testing aligns with your documented architecture.

TDD test setup fails to match project architecture when docs/architecture.md is incomplete or missing. The setup relies on reading architecture signals and existing project constraints to tailor recommendations, so missing documentation forces generic guesses instead of aligned configurations.