Difference between revisions of "Test-driven development"
Jump to navigation
Jump to search
(not sure which category to use) |
m (Uncle Bob's Three Rules of TDD) |
||
| Line 3: | Line 3: | ||
==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]] | ||
Revision as of 15:58, November 26, 2011
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