> Devel::Cover issues aside, has anyone else looked at interesting ways of > making test suites run faster?
One of the drums I beat heavily in my discussion of testing of large projects is that you shouldn't care how long your tests take, so long as they run within the smokebot window. The way we do it is having an hourly cron job that checks out the main CVS project and runs a full blown make test on it. This means that we don't get immediate feedback if a check-in causes a failure, but getting feedback within 59 minutes is close enough to immediate for me. Also, smokebot failures are mailed to the entire department (8 people), so that helps raise the visibility. We've also had to have a 2nd smokebot running, this time hourly on the half hour, to check out and smoke the branch for the parallel project we're running. Also, as an FYI, one of the things I'm going to be adding to Test::Harness soon (Where are those tuits?) is the ability to run the .t files in random order, in the hopes of exciting bugs that are for some reason dependent on order of execution. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
