On Sun, 02 Jan 2005 23:41:11 +1000, Robert Watkins <[EMAIL PROTECTED]> wrote: > > Ron Jeffries wrote: > > Therefore -- in my opinion -- the vector should point in the > > direction of getting all the necessary info instantly, not in the > > direction of tolerating and accommodating slow feedback. > > Shouldn't it point towards effectiveness? Important but non urgent feedback > can certainly be delayed. It is this sort of feedback that the asynchronous > builds are designed to give (as well as being a safety net for the normal > developer builds).
This is the point that I was trying to make: It makes sense to think in terms of horizons... very short term: immediate feedback (ie, syntax error highlighting, unit tests for the class you are changing, etc) short term: Quick feedback, fairly good confidence medium term: slower feedback, very good confidence that everything works. Having said that, if you have an application where you can run ALL of your unit tests, and all of your integration level tests in a short time, there is no reason not to run all the tests pre-checkin, and post checkin while waiting for the feedback. One thing that bothers/confuses me about this discussion: we seem to be mixing up two concepts: -A- offline tests with feedback for convenience (resources, time, as a safety net) -2- offline tests because no one runs tests. for (A), we can argue about what is best, but as long as the tests run and people care and react, the result is good. for (2), you have bigger problems, and automating the tests is a band-aid. -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/
