--- In [EMAIL PROTECTED], Ron Jeffries
<[EMAIL PROTECTED]> wrote:
> On Saturday, January 1, 2005, at 11:39:50 AM, Steve Berczuk wrote:
>
> > Hmm, Why isn't there a place in the process for a set of exhaustive
> > tests that use many resources to ensure that the application works
> > correctly? If you had such tests it is plausable that they may take a
> > long time. I agree that the tests that developers run to ensure that
> > the build works shoud be quick. But I think that you would want to run
> > more exhaustive tests. And run these asynchronously.
>
> Use of "many resources" will not make the tests better.
>
> Running them asynchronously is done because they take a long time.
> The fact that it takes a long time to know if you've done good work
> is the bug. Fix it.
I think the distinction is more clear if we exchange "know if" with
"be confident that"... and then ask how confident?
Running them asynchronously is done because they take a long time and
the additional confidence they provide is not enough to justify
waiting, though it is enough to justify running them.
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/
