Software development methodology involving repetition of a very short development cycle: requirements are turned into very specific test cases, then the software is improved to pass the new tests, only
software development methodology involving repetition of a very short development cycle: requirements are turned into very specific test cases, then the software is improved to pass the new tests, only (en)
"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?" (en)
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. (en)