Ron Jeffries a �crit:
>I'm engaged in a discussion with 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.
>
>I've never seen that happen for any extended period.
>
>How about folks here ... have you encountered such a thing? Tell us about
>it, please?
>
>
I think we accidentally have sometimes two tests for one change, as a
consequence of a refactoring, but that's wiped by proper test
refactoring during the session.
I work with legacy apps, some of those in which the "test-to-code" ratio
is generally not 2:1 but rather 10:10000. Of course I'll read the
article. But currently I'm swimming in an ocean of untested code, so the
assertion about how unconfortable lifeboats sometimes are is quite
questionable to me.
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/
