Test-Driven Development by Example¶
Beck, K. (2003). Test-Driven Development by Example. Addison-Wesley.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Progressive Refinement from Core Model
- Beck's (2003) Test-Driven Development by Example operationalizes this: write a failing test (refine clarity of intent), make it pass with minimal code (baseline solution), then refactor to improve structure while maintaining all test coverage.
This sourceOperationalization of progressive refinement through red-green-refactor cycle preserving test-coverage baseline.
- Beck's (2003) Test-Driven Development by Example operationalizes this: write a failing test (refine clarity of intent), make it pass with minimal code (baseline solution), then refactor to improve structure while maintaining all test coverage.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.
Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:1b40dcfaa5d9 · see in the full table