test-driven-development

Test-driven development starts by writing a failing unit test for the desired feature. You then run the unit tests to confirm the failure and implement minimal production code to make the test pass.

The fails-first cycle in test-driven development follows a Red, Green, Refactor sequence to drive correct behavior and clean design. It improves regression safety by maintaining a robust test suite for new features.

To fix SPEC-V9 gaps or add agent validations using test-first workflows, write tests first to define expected outcomes. You then implement the minimal code required to pass those defined tests.

Yes, you must execute unit tests using pnpm run test:unit prior to implementation to see the failure first. You should also run lint checks with pnpm run check as needed during the process.

Use test-driven development instead of traditional development without tests when you need regression safety and maintainable code. It prevents hidden bugs by guiding design and verification from the start.

Enforcing a test-driven development workflow requires writing failing unit tests before any production code, which slows initial feature delivery. It focuses strictly on unit tests and lint checks within the AssistJur suite.