--- Ron Jeffries <[EMAIL PROTECTED]> wrote:
> [...] David J Anderson, who found an article saying that
> a significant problem with test-driven development is that
> teams tend to fall into the trap of writing too many tests
> and not focusing enough on progress.
> [...]
> How about folks here ... have you encountered such a thing?
> Tell us about it, please?
I've been having that kind of trouble with adding tests to legacy
code systems. Legacy code is remarkably hard to test, so the tests
are complex and often need a lot of work.
But that's not Test Driven Development (TDD). That's a problem that
someone needs to come along and "do the other half of the job" that
the legacy developers couldn't be bothered to do.
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
