Extreme programming practices: Difference between revisions

Revision as of 12:14, 7 September 2017

Revision as of 12:18, 7 September 2017

Line 114:

=== Test driven development ===

[[Unit testing|Unit tests]] are automated tests that test the functionality of pieces of the code (e.g. classes, methods). Within XP, unit tests are written before the eventual code is coded. This approach is intended to stimulate the programmer to think about conditions in which his or her code could fail. XP says that the programmer is finished with a certain piece of code when he or she cannot come up with any further conditions under which the code may fail. For a more intense version of this process, see Uncle Bob's Three Rules of TDD<ref>{{Citecite web|last1=Martin|first1=Robert|title=Three Rules of TDD|url=http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd}}</ref> .

Test driven development proceeds by quickly cycling through the following steps, with each step taking minutes at most, preferably much less. Since each user story will usually require one to two days of work, a very large number of such cycles will be necessary per story.