dev-tdd

Test-Driven Development using the RED-GREEN-REFACTOR cycle requires writing a failing test first, implementing the minimum code to pass that test, and then refactoring. This Skill guides you through each phase with strict execution gates and file-based logging.

The best way to ensure failing tests are written before implementation is to enforce mandatory testing within your TDD workflow. This Skill mandates that tests are written and explicitly observed failing before any functional code is developed.

Yes, this TDD workflow supports both unit testing and e2e testing. It enforces the RED-GREEN-REFACTOR cycle across both testing types to promote robust code quality and reliable software development.

To write tests first for a new user authentication module, you start by writing failing tests for login, registration, and password reset functionalities. Only after observing the failing tests do you implement the code to make them pass.

Code quality degrades during refactoring without mandatory tests because there is no safety net to catch regressions. Enforcing the RED-GREEN-REFACTOR cycle ensures tests remain passing while you improve the code structure.

Yes, you can use this TDD approach for general development without external dependencies. It operates independently with file-based logging to track your testing cycle, requiring no additional libraries or frameworks to function.