On Fri, Apr 02, 2004 at 11:55:36PM +0100, Fergal Daly 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,
Coming soon to Devel::Cover (well, on my TODO list anyway): - Provide an optimal test ordering as far as coverage is concerned - ie tests which provide a large increase in coverage in a short time are preferred. There should also be some override to say run these tests first anyway because they test basic functionality. - Report which tests cover specific subroutines, so that if you make a change to a certain subroutine you can run only the tests which exercise that subroutine. This could also be done at a lower level, but that is probably not very useful. All this is supposing that tests take quite a while to run. I wonder how many people have test suites that take more than a few minutes to run. One advantage of long running tests is that is gives you a bit of time to actually think about what you are doing. Unless you go and read some mail or chat on IRC, I suppose. -- Paul Johnson - [EMAIL PROTECTED] http://www.pjcj.net
