Editing Test-driven development (section)

== History ==
Software engineer [[Kent Beck]], who is credited with having developed or "rediscovered"<ref name="Quora2012May11">{{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> the technique, stated in 2003 that TDD encourages simple designs and inspires confidence.<ref name=Beck />

{{Blockquote
| 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>
}}