3 ms·
Aren't those both the same thing? (Not being sarcastic; I'm genuinely confused.) http://stackoverflow.com/questions/3192090/test-driven-development-vs-test-fir
by kens 12y ago
Aren't those both the same thing? (Not being sarcastic; I'm genuinely confused.)
http://stackoverflow.com/questions/3192090/test-driven-development-vs-test-first-development http://stackoverflow.com/questions/3192090/test-driven-devel...
- ZoFreX 12y agoThe way I was taught is that TDD is writing a test, making it pass, repeat - the red-green-refactor cycle. Test first could include "write 200 tests that all fail, then write all the code to make them pass". Somewhat substantiated by this answer: http://stackoverflow.com/questions/334779/is-there-a-difference-between-tdd-and-test-first-development-or-test-first-prog http://stackoverflow.com/questions/334779/is-there-a-differe...
- icefox 12y agoWhile TDD originally stood for writing tests first and then code for the majority of people TDD means you have tests. I have encountered countless people that say they are using TDD, but writing tests after or during coding and not before. To them test driven development means that you are done with a task when the test passes. In comparison to before where there was no tests it is easy to see how the new way of developing is related to tests so they think they are doing TDD. So I would say that "classic" TDD or test first development is dead. It also didn't help how TDD was shown in a study to not work out very well. I don't have it off hand, but it was talked about in the "Making Software" book http://www.amazon.com/exec/obidos/ASIN/0596808321/wwwicefoxnet-20 http://www.amazon.com/exec/obidos/ASIN/0596808321/wwwicefoxn...