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.
  • So, not so clear what you need me to do (too little caffeine today). You want me to drop the Test::Pod stuff? Sorry, but that link you gave regarding author best practices it broken for me. Just let me know what to do and I will cut a release asap. John
    --
    Waiting on the Road to Eventually, I lost my Place On Line
    • 1. Remove all mention of the author test modules from META.yml

      2. As a bonus, you can change pod.t to something like this

      #!/usr/bin/perl

      # Test that the syntax of our POD documentation is valid
      use strict;
      BEGIN {
              $| = 1;
              $^W = 1;
      }

      my @MODULES = (
              'Pod::Simple 3.07',
              'Test::Pod 1.26',
      );

      # Don't run tests during end-user installs
      use Test::More;
      unless ( $ENV{AUTOMATED_TESTING} or $ENV{RELEASE_TESTING} )

      • I realize you are only suggesting this for the pod tests.  For those tests, this is innocuous enough.  However, as chromatic pointed out, cargo cult programming exists.  I'd prefer to give the cargo cult programmers as few chances to happen across code that skips all tests for people installing via CPAN/CPANPLUS, especially since some of them may not run any tests on their own boxes (even though they have them.)

        • You prefer to prioritise the people that would copy and paste author tests into their own modules ahead of everyone everywhere that installs modules for any reason at all?

          That seems like prioritising a small group with a rare situation ahead of an enormous group with common situation.