Content deleted Content added
Citation bot (talk | contribs) Add: date, authors 1-1. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Abductive | Category:Extreme programming | #UCB_Category 22/41 |
→History: Moved citations in <ref> |
||
Line 16:
| text = The original description of TDD was in an ancient book about programming. It said you take the input tape, manually type in the output tape you expect, then program until the actual output tape matches the expected output. After I'd written the first xUnit framework in [[Smalltalk]] I remembered reading this and tried it out. That was the origin of TDD for me. When describing TDD to older programmers, I often hear, "Of course. How else could you program?" Therefore I refer to my role as "rediscovering" TDD.
| author = [[Kent Beck]]
| title =
| source = "Why does Kent Beck refer to the 'rediscovery' of test-driven development? What's the history of test-driven development before Kent Beck's rediscovery?"<ref>{{cite web|url=http://www.quora.com/Why-does-Kent-Beck-refer-to-the-rediscovery-of-test-driven-development |title=Why does Kent Beck refer to the "rediscovery" of test-driven development? |author=Kent Beck | date=May 11, 2012 |access-date=December 1, 2014}}</ref>
}}
Line 23:
[[File:TDD Global Lifecycle.png|thumb|A graphical representation of the test-driven development lifecycle]]
The TDD steps vary somewhat by author in count and description, but are generally as follows. These are based on the book ''Test-Driven Development by Example'',<ref name=Beck>{{cite book |last=Beck| first=Kent |title=Test-Driven Development by Example |publisher=Addison Wesley |___location=Vaseem |date=2002-11-08 |isbn=978-0-321-14653-3}}</ref> and Kent Beck's
;1. List scenarios for the new feature
| |||