Difference between revisions of "Test-driven development"
Jump to navigation
Jump to search
(not sure which category to use) |
DavidB4-bot (talk | contribs) m (→top: clean up) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | With test-driven development, you write your test first, then you write just enough code to make the test pass.<ref> [http://weblogs.asp.net/russnem/archive/2007/01/17/shaking-things-up-scrum-agile-and-tdd.aspx Shaking Things Up: Scrum, Agile, and TDD] - Russ Nemhauser</ref> | + | With '''test-driven development''', you write your test first, then you write just enough code to make the test pass.<ref>[http://weblogs.asp.net/russnem/archive/2007/01/17/shaking-things-up-scrum-agile-and-tdd.aspx Shaking Things Up: Scrum, Agile, and TDD] - Russ Nemhauser</ref> |
==Notes== | ==Notes== | ||
{{reflist}} | {{reflist}} | ||
| + | |||
| + | ==Links== | ||
| + | *[http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd Uncle Bob's Three Rules of TDD] | ||
[[Category:Software Engineering]] | [[Category:Software Engineering]] | ||
[[Category:Computer Programming]] | [[Category:Computer Programming]] | ||
Latest revision as of 15:05, June 23, 2016
With test-driven development, you write your test first, then you write just enough code to make the test pass.[1]
Notes
- ↑ Shaking Things Up: Scrum, Agile, and TDD - Russ Nemhauser