VolkerG schrieb am 29. Januar 2013 21:34
> "[...]
> A systematic review that aggregated the available evidence
> about the effectiveness of TDD found that TDD does not have
> a consistent effect on productivity. ...
Well, I am not sure if this is a result of teams not (yet) being
ready for that development style. Maybe they simply need some fine
tuning of the processes and more experiences...
> - Tests are weighted more heavily than the code
> The emphasis of composing tests before the actual code of the
> application adds more importance to the tests than the actual
> code itself. This is ... idiotic and wrong in
> every way, shape, and form.
Again I disagree. Developers of productive code have a different view
on the application architecture and the business cases, compared with
what test developers have. In fact it is reduced to what are the
requirements, what do they mean and how are the business cases. When
the tests reflect those reqs, BCs and the architecture, than the
might help the code developers to create the right code by simply
passing those tests. If the code developers disagree with specific
test the can escalate and argue for a change of that test.
As tests only make sense for units in a given architecture, one can
not create tests for units that are not yet defined (not even by
requirements).
Just my € 0.02