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
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
TDD is not about testing, it's about development.
--
Best regards,
Dennis Schetinin
2014-04-23 19:35 GMT+04:00 Sven Van Caekenberghe :
> 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-
Testing has become more necessary in the context of Continuous
Integration and automated building. You can't have those without test
coverage.
On the other hand, TDD is rather difficult with tools that doesn't
allow you to develop inside the debugger, which is basically
everything out there that i
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
