II.
Methodology overview
Reference · livemethodology:tdd
Test-Driven Development (TDD) overview
The classic Red/Green/Refactor loop per feature unit. For each unit of work: Red (write a failing test expressing the next small requirement), Green (write the minimum code to make it pass), Refactor (clean up with tests still green). An outer loop drives the full feature by sequencing units. Stops early if a unit cannot reach green within maxIterations as a signal to reconsider the design rather than pile on more code.
Attributes
displayName
Test-Driven Development (TDD)
description
The classic Red/Green/Refactor loop per feature unit. For each unit of work:
Red (write a failing test expressing the next small requirement), Green (write
the minimum code to make it pass), Refactor (clean up with tests still green).
An outer loop drives the full feature by sequencing units. Stops early if a unit
cannot reach green within maxIterations as a signal to reconsider the design
rather than pile on more code.
methodologyKind
quality-focused
origin
Kent Beck
yearIntroduced
1999
Outgoing edges
applies_to1
- domain:software-engineering·DomainSoftware Engineering
Incoming edges
follows_methodology1
- lib-process:shared--tdd·LibraryProcesstdd