I think that makes a lot of sense.
On 1/15/09 3:43 PM, "Niclas Hedhman" <[email protected]> wrote: > On Thu, Jan 15, 2009 at 10:35 PM, scott comer (sccomer) > <[email protected]> wrote: >> fyi: the long running unit tests are fooling around with timing tests and so >> they take awhile >> because they are waiting for stuff to happen. it's a granularity issue. if >> the timeouts are >> too short, they fail on some platforms, notable vmware. > > I don't have problem with long/slow running tests. Just isolate them > and make them part of a continuous integration test "profile" and the > release "profile", so that not too much time are eaten up in the > edit-compile-test cycle. > > Cheers > Niclas -- James Dixson Manager, Software Development CUAE Engineering, Cisco Systems (e) [email protected] (p) 512-336-3305 (m) 512-968-2116
