test-driven-development

The test-driven development RED-GREEN-REFACTOR cycle enforces writing a failing test, writing production code to pass it, then refactoring. This strict test-first workflow ensures code quality, maintainability, and correctness by preventing bugs before implementation.

To implement test-first development, you must mandate writing failing tests before any production code. This methodology guides you through an iterative verification process, ensuring comprehensive tests verify each aspect of the feature flow before implementation code is committed.

You should use strict test-driven development to enforce a rigorous test-first workflow, ensuring code quality and correctness. By prioritizing test creation before production code, it prevents the introduction of bugs and maintains code integrity through specific verification steps.

This test-driven development methodology addresses testing anti-patterns and applies anti-rationalization rules to maintain code integrity. It enforces strict verification steps and output requirements throughout the RED-GREEN-REFACTOR cycle, preventing common TDD workflow failures.