test-first

Test-driven development begins by writing an end-to-end test that describes desired behavior through public interfaces, then implementing minimal code to pass it. This approach ensures tests guide design decisions rather than internal implementation details.

The Prove-It pattern is a bug-fix workflow where you write a failing test reproducing the reported bug, implement the fix, then verify no regressions occur. This disciplined approach ensures end-to-end software quality throughout the process.

Integration tests should describe desired behavior through public interfaces rather than internal implementation details. This ensures test coverage guides design decisions and maintains end-to-end software quality throughout iterative refactoring.

A structured TDD workflow involves planning, test creation, tracer bullets, incremental development loops, and thoughtful refactoring. This disciplined approach delivers reliable software by enforcing testing through public interfaces.

Test-driven development emphasizes public interface testing to focus on behavior over implementation. This ensures tests describe desired functionality rather than internal details, enabling iterative refactors without breaking end-to-end software quality.

Yes, TDD patterns apply to both scenarios. For new features, write end-to-end tests describing desired behavior. For bug fixes, use the Prove-It pattern: write a failing test, implement the fix, then verify no regressions.