test-driven-development

Test-driven development starts by writing a failing test that defines expected behavior, then writing minimal implementation code to pass that test, and finally refactoring while keeping tests green.

The RED-GREEN-REFACTOR cycle is a test-driven development workflow where you write a failing test (RED), write minimal code to pass it (GREEN), and then clean up the implementation (REFACTOR) to prevent regressions.

To enforce TDD during bug fixes, write a failing test that reproduces the specific bug, write the simplest code to make that test pass, and refactor the implementation to ensure code reliability and prevent future regressions.

Yes, test-driven development workflows use terminal commands to verify test failures, such as running pytest tests/test_feature.py::test_name -v to ensure the initial failing test behaves as expected before implementation.

Yes, test-driven development integrates with delegate_task for subagent workflows, guiding subagents through the strict RED-GREEN-REFACTOR cycle to ensure code quality across distributed software development tasks.

Test-driven development is used instead of post-implementation testing to enforce rigorous workflow requirements upfront, ensuring code is written to meet specific tested criteria, thereby reducing bugs and improving overall code reliability.