On Sat, 1 Jan 2005 11:03:09 -0500, Ron Jeffries <[EMAIL PROTECTED]> wrote: > > On Saturday, January 1, 2005, at 10:50:09 AM, Steve Berczuk wrote: > > > But what if you have a "complete" set of tests that takes, say, an > > hour.... > > This is the bug. We should fix it.
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. I'm trying to describe a layered approach: 1. While coding: Incremental builds and Unit Tests for code you are working on. 2. Before Check in: Update from Codeline, Full Build (when possible) but perhaps not from a clean checkout, and the reasonable set of tests that run quickly. 3. After check in: Automated FULL BUILD (from a clean checkout), FULL set of COMPLETE tests. Perhaps what differs between what I am saying and what Ron is saying is that there is also a 3(-) step where we run a full build from a clean checkout, but the quick set of tests, on the integration machine? (and wait for the results?) I think that, in practice, you would see the problems from the first step of the integration build quickly enough to make timely changes... Steve -- Steve Berczuk | [EMAIL PROTECTED] | http://www.berczuk.com SCM Patterns: Effective Teamwork, Practical Integration www.scmpatterns.com 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/
