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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Is that a common problem, installation failures? Instead of installing the tests somewhere can't it just do some kind of -I to get @INC set?

    I don't know of any traditional location for tests in production and I'd rather there not be a pile of clutter under my @INC directories while a dozen different people all decide to use some different scheme for storing their tests somewhere.
    • I want you to install your (Test::Class-based) tests as normal modules so I can reuse it when I reuse your modules.

      • That is just the mental shove I needed to see why I'd possibly ever care about Test::Class. Thanks!
        • There are plenty of other reasons to use Test::Class. Do you have thirty t/*.t programs? You've just loaded the perl runtime at least 30 times (probably more). You've also probably reloaded the tested modules many times and possibly duplicated a lot of test code. With Test::Class, you only load the Perl interpreter once and the associated modules once. Large test suites can run much faster and are easier to refactor.

          And inheriting tests to ensure that derived classes don't break their parents makes m