Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

Ovid
  (email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Tuesday June 24, 2008
06:08 AM

Test::Aggregate versus Test::Class

[ #36761 ]

Still working on Test::Aggregate, but so far it works well. Currently we have tests which would normally take 13m25s running in 4m17s. I call that a win.

Regrettably, this might kill Test::Class adoption for us. Test::Class also runs the code in a single process, but the inherited tests push the test time up to an unacceptable level. This is disappointing to me as I would love to convert almost all of our tests over to Test::Class. It's one of the best test modules out there.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • but the inherited tests push the test time up to an unacceptable level

    I'm curious - why are the inherited tests pushing the test times up? Is it just the OO overhead or am I doing something stupid and slow somewhere? ;-)
    • I'm being overly verbose in my answer not because I think you need this, but I assume that most people reading this have never used Test::Class.

      It's not your fault at all. The vast majority of time for most test suites I work with is either I/O or the sheer number of tests. Since Test::Class inherits tests (as it should!), then when I run Test::Pips3::Report::Query::Validation::ExceptionsByPeriod, which naturally inherits from Test::Pips3::Report::Query::Validation, I get all non-overridden superclass t

      • Hmmm... so it might be nice to (optionally) not inherit tests for a particular test run.... Added to the to do list :-)