tdd-workflow

You enforce a strict red-green-refactor TDD cycle in TypeScript by applying a 7-state state machine that requires every message to declare its current state. This governs the progression through PLANNING, RED, GREEN, REFACTOR, VERIFY, BLOCKED, or VIOLATION, ensuring tests drive design.

A TDD state machine is a governance mechanism that maps development workflow into seven explicit states: PLANNING, RED, GREEN, REFACTOR, VERIFY, BLOCKED, and VIOLATION. It structures workflow by requiring every interaction to begin with a current state prefix, forcing disciplined transitions.

You integrate vitest-mock-extended and dependency injection for deterministic testing by combining them with the fn(args, deps) pattern and typed error handling. This ensures type-safe, test-driven behavior and provides deterministic mock generation for your dependencies.

Yes, this TDD workflow works for chat-driven code generation tasks. The state machine explicitly applies to both code and chat-driven tasks, ensuring the assistant follows the test-first discipline during interactive feature implementation.

You use the BLOCKED or VIOLATION state in test-driven development when progress halts or the red-green-refactor cycle is broken. The state machine transitions to VIOLATION when workflow discipline is compromised, and BLOCKED when external issues prevent forward movement.

Yes, you can apply typed error handling alongside a vitest TDD workflow. Typed error handling is a required integration that works with vitest-mock-extended and the fn(args, deps) pattern to provide deterministic, type-safe behavior throughout the state machine cycles.