3 ms·
Is that a problem with TDD, or is that just a problem with teams choosing to use bad tooling and processes? I've seen teams waste a lot of time trying to get v
by Pacabel 12y ago
Is that a problem with TDD, or is that just a problem with teams choosing to use bad tooling and processes?
I've seen teams waste a lot of time trying to get various CI systems integrating with various TDD frameworks, generating lots of reports that nobody really ever looks at. Or they waste a lot of time writing elaborate frameworks that build upon some existing TDD framework.
But all of that has basically nothing to do with TDD. It has nothing to do with the act of writing tests first, and developing the actual code based on the success or failure of those tests.
- crdoconnor 12y agoWriting tests takes time and is an investment and should be treated as such. Too many zealots try to pretend that it's a zero cost design habit.
- skj 12y agoI think that they would argue that it's a positive net benefit design habit.
- crdoconnor 12y agoThe OP mentions a number of antipatterns that only come about due to TDD. So no, not necessarily. Not unless it's done correctly and in the right circumstances.