moai-workflow-tdd

A test-driven development workflow is automated through the RED-GREEN-REFACTOR cycle, guiding teams to define behavior with failing tests before writing minimal code to pass and refactoring. This approach reduces ambiguity and prevents scope creep across frontend, backend, and integration work.

The RED-GREEN-REFACTOR cycle is a test-first development loop where you write a failing test (RED), implement minimal code to pass the test (GREEN), and improve the code structure while keeping tests green (REFACTOR). This disciplined process ensures repeatable quality.

Yes, test-driven development integrates with Domain-Driven Design (DDD) to preserve behavior during refactors. It also supports characterization tests for existing code, ensuring that structural improvements do not alter core domain logic.

Test-first development enforces minimum quality gates including specific test coverage expectations and TRUST 5 validation. These governance aids ensure that the software meets defined behavioral specs and quality metrics throughout the development loop.

Yes, the TDD workflow provides collaboration and role-based execution hints tailored for manager-tdd, expert-backend, expert-frontend, and expert-testing roles. This ensures structured coordination across the team during the test-first development phases.

The best way to start a TDD session is by defining the SPEC, writing a failing test (RED), implementing minimal code to pass the test (GREEN), and refactoring the implementation while keeping tests green (REFACTOR). This phase-guided workflow ensures structured development.