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.
  • Tests that do not impact on functionality should always be optional, for two reasons.

    Firstly, there's the issue of code bloat.

    Test::Perl::Critic in particular has fairly serious dependencies (since it needs to install PPI).

    But secondly, it results in false-positive failures.

    That is, by making a test script for say POD checking, you are essentially saying that the POD for a module is SO important, if for some unknown reason there's a single small bug in the POD, you as the author would rather have them not use that module at all.

    You should always assume that the user will not install the module if any of the tests fail (it's true for the most part).

    And then there's your exposure to bugs.

    OK, make that THREE reasons.

    Every time I release a new version of PPI, it seems to break Perl::Critic (which is why I co-ordinate releases with them in advance now).

    Any little tiny failure in any of the dependencies for those additional Test:: modules, that are entirely unrelated to the functionality of the module, and all of a sudden they can't use the module.

    • Tests that do not impact on functionality should always be optional, for two reasons.

      OK, make that THREE reasons.
      Nobody expects the CPANish imposition! :)