specialist-tdd-guide

Test-first development is enforced by automating the Red-Green-Refactor cycle, requiring a failing unit test to be written before feature implementation. This discipline ensures broad test coverage and reduces codebase waste.

The Red-Green-Refactor cycle is a test-first workflow where you write a failing test, write code to make it pass, then refactor. Use it across unit, integration, and E2E testing to ensure comprehensive coverage and meaningful tests.

Start test-first discipline by writing a failing unit test for the specific feature you plan to implement. Run your tests to see them fail, then write the minimum code required to turn them green before refactoring.

Yes, this TDD workflow supports integration testing and end-to-end tests alongside unit tests. It provides specific templates and conventions to guide developers through designing and maintaining all three levels of tests.

The best way to achieve comprehensive test coverage is by enforcing a test-first mindset through the Red-Green-Refactor workflow. Using provided templates and conventions ensures you write clear, meaningful tests across all project layers.

Yes, automating TDD enforcement requires clear frontmatter metadata to function properly. Defining this metadata allows the system to support the TDD workflow and provide accurate templates and coverage assessment.