On Wed, Jan 29, 2014 at 6:50 AM, Todd Rinaldo wrote:
> I’m looking at using TAP::Harness to process our test suite. Up to now
> we’ve been using some home grown code that IMHO is a heroic attempt to
> re-implement TAP::Harness.
>
> It seems to do everything we need with one exception. We have rul
I don't know how easy that is to do with Test::Harness, though my
App::Prove::Plugin::ProgressBar[1] might put you in the right direction.
Alternatively, Test::Class::Moose[2] has a "reporting" feature that reports on
timing and breaks it down into system, real and user time. You should be able
