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.

Testing Installed Modules: Opening a Can of Worms 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Because way too many tests are written with the assumption that they will be running from within an unpacked module distribution.

    Which is exactly the situation that the retest feature in Module::Build assumes, so I don’t quite see why this is a problem.

    • The problem is that installed modules have more to them than the .pm files, and those are basically the only parts of your installation you're going to be testing when you use retest.

      Tests for scripts will be tests on the scripts in the distribution, not the ones installed. Likewise for all the other things that a distro can have.

  • It was my original request. I want to make sure that things still work even though I've upgraded a module low down in the dependency tree. I don't want to solve this in every case. I don't want the moon on a stick. I just want something simple, like copying t/* somewhere during install. I was afraid of posting about it because I knew people would go overboard and get philosophical. And look what happened when Ovid mentioned it...
    • I'm interested in the future of the module ecosystem.

      This was an opportunity for me to get philisophical, but it wasn't your fault. :)
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.