test-driven-development

This methodology mandates writing a failing test first, implementing minimal code to pass it, and then refactoring safely. It ensures every line of production code is verified and intentional.

Writing tests before implementation is best achieved by building features in end-to-end slices, known as vertical tracer bullets. This approach prevents brittle test suites by guiding you to write a failing test case first before committing production code.

Yes, test-driven development applies to bug fixes and refactoring efforts alongside new feature development. It ensures high code quality and prevents regressions by requiring tests to be written before any production code is modified.

Yes, this test-driven development approach requires terminal access to execute test suites and file system access to manage test and production code files. This access allows the agent to verify failing tests and implement code directly.

Writing all tests at once often results in brittle test suites because it lacks end-to-end validation. Encouraging vertical tracer bullets builds features in complete slices, ensuring logic is sound and requirements are met iteratively.