TDD is great if you don't know the domain you're modeling, or if it isn't completely specified. Because you end up having the required functionality completely tested. On the other hand, if you are an expert in the domain, you'll implement features that are beyond the required (initial) specs, so you'll code ahead of the specs, and doing everything TDD will be a burden. Regards! Esteban A. Maringolo 2014-04-23 15:11 GMT-03:00 kilon alios <kilon.alios@gmail.com>:
TDD does not convince me much either, I see it as a convenience but I am not so sure it really worths its time. Maybe because there too few coders out there that would make changes that will massively affect the system, or they wont do some form of testing anyway.
I can see the benefit of TDD when you code apps or libs with objects that are highly dependent on each other and you want to make sure you dont brake anything, but I doubt thats a common case.
And not even Pharo has convinced me to use tests, though that is the common practice.
On Wed, Apr 23, 2014 at 8:18 PM, Dennis Schetinin <chaetal@gmail.com> wrote:
TDD is not about testing, it's about development.
--
Best regards,
Dennis Schetinin
2014-04-23 19:35 GMT+04:00 Sven Van Caekenberghe <sven@stfx.eu>:
More or less what I think: testing is necessary and should be pragmatic & fun, not a dogma
http://david.heinemeierhansson.com/2014/tdd-is-dead-long-live-testing.html