moai-workflow-tdd

To start test-driven development, you initiate a new feature cycle by writing a failing test that specifies the desired behavior, then implement the minimal code to pass it, and finally refactor for clarity.

The red-green-refactor cycle is the core TDD loop where you write a failing test, implement the minimal code to make it pass, and then improve the code's clarity and efficiency without changing its behavior.

Yes, you can use test-first development for building API endpoints and isolated modules, as it drives implementation by defining expected outcomes and verifiable behavior through testing frameworks before writing the actual code.

Test-driven development requires adherence to test-first principles and the use of testing frameworks for verification, but it does not mandate a specific framework, allowing flexibility based on your software environment.

You should avoid using the TDD methodology when building exploratory prototypes or throwaway scripts where defining strict behavior specifications upfront would hinder rapid iteration and delay initial development.

Writing tests before code ensures software is built with a focus on quality and verifiable behavior from the outset, establishing clear expected outcomes that drive the implementation and reduce defects.