Evgeny wrote: > The know: > - how many unit tests were executed each run > - how much time each unit test took to run (and the total time) > - which unit tests passed, and which failed > - the behavior of some tests over time (a bad test can randomly > fail/pass for example)
As an aside, have a look at Smolder. http://sourceforge.net/projects/smolder Here it is live testing Parrot. http://smolder.plusthree.com/app/public_projects/smoke_reports/8 > I wont argue that plan counter does not have its use. It probably > does. But what it also does is annoy the developer. That is why you > would probably see "no_plan" used in most of the testing code in the > wild (I am not talking about CPAN). I agree. The plan is a big wonkin hammer that's usually unnecessary. That's why there's no_plan. And soon the safer done_testing(). I'd be fine with someone revising the Test::More and Test::Tutorial docs to make it less plan-centric now that done_testing() is there. -- package Outer::Space; use Test::More tests => 9;
