tdd-stub-first

Stub-first test-driven development is a TDD methodology where you create file structures, stubbed methods with placeholder logic, and end-to-end tests against these stubs before actual implementation to catch design flaws early.

To implement a TDD workflow using the stub-first strategy, define expected behavior through stubs and end-to-end tests first, implement the actual code logic next, and finally add detailed unit tests.

Test-driven development with stubs explicitly enforces rules against mocking LLMs. Instead, it mandates regression testing to ensure robust and verifiable code throughout the development process.

You should use a stub-first methodology when developing new features to ensure early verification. It streamlines the process by validating end-to-end tests pass against stubs before you write full implementations.

Stubbed methods in test-driven development contain placeholder logic, meaning they only verify structural design and end-to-end test flow early on, requiring full implementation and detailed unit tests later for actual code coverage.