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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Test::Aggregate versus Test::Class 3 Comments More | Login | Reply /

 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 :-)
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.