BTW... Which slow test ? It takes 46 Seconds here to run all tests .. So whats the problem ? If someone really still use a 686 with 66 MHz its time to upgrade the hardware :-P
bye Norman Norman Maurer schrieb: > Stefano Bagnara schrieb: > > </SNIP> > >>>> I don't consider slow tests as bad tests. They are just inappropriate >>>> for a ad hoc results. Even if they took an hour it's okay, but we need >>>> to find a way not to force people to run them all the time. >>>> >>> Not agreed. According to my experience unit tests should be fast and >>> easy. Otherwise your unit test setup is flawed or could be simplified. >>> Other tests, of course, for example integration or compliance test >>> could take much more time. >>> >>> Bernd >>> >> The problem here is that most of our tests are not really unit tests >> but more similar to integration tests. >> >> Imho 8 minutes is not a long running test suite. I have test suites >> running for hours in big projects. >> >> It is better a long running test than no test. If a test can be made >> faster ok, but we should not limit the maximum time for a test. >> >> Stefano >> >> > > I agree with Stefano.. I really don't care how long a test need to run.. > Im just happy to see all these "green" lights after the run is complete :-) > > bye > Norman > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > !EXCUBATOR:1,45585f0653072787113538! > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
