On Fri, Apr 02, 2004 at 04:59:41PM -0600, Andy Lester wrote: > > Even if you have a smoke bot, you presumably run the tests (depends on the > > size of the suite I suppose) before a checkin and it's convenient to know > > that the first failure message you see if the most relevant (ie at the > > lowest level). Also when running tests interactively it's nice to be able to > > save even 30 seconds by killing the suite if a low level test fails, > > Sure, but even better is to run only the tests that need to be run, > which is a key part of prove. You can run "prove -Mblib t/mytest.t" > instead of the entire "make test" suite.
If the suite's big enough to warrant a bot then that makes sense but many of my modules have test suites that complete within a fairly short time. I tend to run the relevant test until it passes and then run the suite before checkin. I can pipe the verbose output the whole suite into less and know that the first failure is probably the most important one. F
