TDD

E440641

TDD (Test-Driven Development) is a software development practice where automated tests are written before the production code, guiding design and ensuring continuous verification of functionality.

All labels observed (2)

Label Occurrences
Test-Driven Development 3
TDD canonical 2

How this entity was disambiguated

Statements (52)

Predicate Object
instanceOf software development practice ⓘ
software testing methodology ⓘ
alsoKnownAs test driven development ⓘ
test-first development ⓘ
appliedIn functional programming ⓘ
object-oriented programming ⓘ
procedural programming ⓘ
benefit better modular design ⓘ
earlier defect detection ⓘ
higher confidence in code changes ⓘ
improved documentation through tests ⓘ
living regression test suite ⓘ
challenge difficulties with legacy codebases ⓘ
initial learning curve ⓘ
perceived slower initial development speed ⓘ
coreIdea maintain a fast feedback loop through automated tests ⓘ
use tests to drive software design ⓘ
write automated tests before writing production code ⓘ
emphasizes automated unit tests ⓘ
design through examples ⓘ
fast feedback ⓘ
frequent test execution ⓘ
small incremental changes ⓘ
testability of code ⓘ
fullName Test-Driven Development NERFINISHED ⓘ
goal clarify requirements ⓘ
enable continuous verification of functionality ⓘ
encourage simple design ⓘ
improve code quality ⓘ
reduce defects ⓘ
support safe refactoring ⓘ
introducedBy Kent Beck NERFINISHED ⓘ
popularizedIn Extreme Programming community NERFINISHED ⓘ
relatedTo Acceptance Test-Driven Development ⓘ
Agile software development ⓘ
Behavior-Driven Development NERFINISHED ⓘ
Extreme Programming NERFINISHED ⓘ
clean code practices ⓘ
continuous integration ⓘ
refactoring ⓘ
unit testing ⓘ
requires automated testing framework ⓘ
repeatable test suite ⓘ
step refactor code while keeping tests passing (refactor) ⓘ
write a failing test (red) ⓘ
write minimal code to make the test pass (green) ⓘ
typicalCycle red-green-refactor ⓘ
typicalTestLevel component tests ⓘ
unit tests ⓘ
usedFor guiding API design ⓘ
preventing regressions ⓘ
specifying expected behavior in executable form ⓘ

How these facts were elicited

Referenced by (5)

Full triples — surface form annotated when it differs from this entity's canonical label.

Minitest → supports → TDD ⓘ
Sinon → relatedConcept → TDD ⓘ
Kent Beck → fieldOfWork → TDD ⓘ
this entity surface form: Test-Driven Development
Kent Beck → notableFor → TDD ⓘ
this entity surface form: Test-Driven Development
Kent Beck → pioneerOf → TDD ⓘ
this entity surface form: Test-Driven Development