Orchestrate Disciplined Test-Driven Development

This is an expert-level persona for orchestrating test-driven development across complex, multi-agent, and multi-team projects. It enforces the complete red-green-refactor cycle, coordinates specialized testing agents (unit, integration, E2E), and covers TDD methodology variants - Classic/Chicago School, London School (mockist), Acceptance Test-Driven Development, Behavior-Driven Development, outside-in and inside-out TDD, and hexagonal-architecture TDD with ports and adapters.

It spans the practical machinery of TDD at scale: test suite architecture (test pyramid, categorization, isolation, shared fixtures), TDD metrics (cycle time, coverage, mutation testing, technical debt), multi-language and multi-framework support (Java/JUnit, C#/NUnit, Python/pytest, JavaScript/Jest and Mocha, Go/testing package), build-system and CI integration (Maven, Gradle, npm, Cargo, MSBuild), property-based and advanced testing techniques (QuickCheck, Hypothesis, fast-check, mutation testing, fuzzing, contract testing, snapshot testing, chaos engineering), legacy-code characterization (golden master testing, approval testing, seam identification), and cross-team TDD governance and coaching.

Use it when establishing or scaling TDD discipline across a team or organization: setting up multi-agent test orchestration, designing a TDD metrics dashboard, coordinating legacy-code refactoring with a characterization-test safety net, or building a cross-team TDD governance framework. It's aimed at coordination and process-level TDD questions, not just "write me one unit test."

It is not the right tool for a single quick test-writing task with no orchestration or governance dimension, and it does not replace language- or framework-specific testing documentation - it assumes familiarity with the listed frameworks rather than teaching them from scratch.

Input is a TDD-related goal - starting TDD on a new microservices project, coordinating parallel test development across agents, or designing compliance/quality-gate enforcement. Output is a structured TDD workflow: cycle-enforcement mechanisms, agent task delegation for test development, metrics/dashboard design, or a governance framework, following an eight-step response approach - assess readiness, establish discipline, orchestrate workflows, implement metrics, coordinate refactoring, optimize execution, monitor compliance, scale practices.

Works across a wide language/framework matrix (Java, C#, Python, JavaScript, TypeScript, Go; JUnit, NUnit, pytest, Jest, Mocha), build tools (Maven, Gradle, npm, Cargo, MSBuild), CI pipelines, IDE TDD plugins, and cloud-native/containerized test environments. Draws on foundational TDD literature (Kent Beck's Test-Driven Development by Example, Growing Object-Oriented Software Guided by Tests) and integrates property-based testing tools like QuickCheck, Hypothesis, and fast-check.

Engineering leads, test architects, and platform teams introducing or scaling TDD practice across multiple developers, agents, or repositories, rather than an individual developer writing a single isolated test case.