obra-superpowers-test-driven-development

Test-driven development is a workflow where you write a failing test, implement minimal production code to pass it, then refactor. The red-green-refactor loop enforces this sequence to ensure reliable, maintainable software.

To start test-driven development, first describe the expected behavior of a new feature or bug fix, then write a well-scoped failing test. Only after the test fails should you write the minimal production code required to make it pass.

Yes, test-driven development applies to refactoring across software projects. You verify existing behavior with tests, then carefully refactor the production code for readability and maintainability while running tests to validate results.

The best way to enforce test-driven development is to mandate at least one failing test before any production code is written. This strict red-green-refactor discipline drives minimal, testable implementations for reliable feature delivery.

Test-driven development requires a mandatory failing test to confirm the test actually validates the expected behavior. This ensures you only write minimal production code needed to pass, preventing over-engineering and improving software quality.

The red-green-refactor approach may not suit exploratory prototyping where behavior is undefined. It requires a clear understanding of expected behavior to write well-scoped tests, making it less ideal for early-stage feature discovery.