in reply to POD Standards

Please be sure to look at Test::Pod and Test::Pod::Coverage to automate your checking. I think that Test::Pod::Coverage ought to be extensible enough to handle your substitute.

xoxo,
Andy

Replies are listed 'Best First'.
Re^2: POD Standards
by jZed (Prior) on Jan 07, 2006 at 19:24 UTC
    But if you include your POD tests as part of your distributed module, please consider using "skip unless require Test::Pod" logic.

    I recently tried to install a module on my ISP and it installed and tested fine except the one test that depended on Test::POD which failed because Test::POD wasn't installed. Off CPAN.pm went to intall Test::POD and its many prereqs and somewhere in that very long list it came on something that needed Module::Build which refused to install (No, please let's not get into a MakeMaker/Build war). Yes the situation is b0rked and I should fix it, but I needed the original module running right away. I ended up doing a force install on the original module since its only failed test was the one requiring Test::POD.

    Personally, I don't think it's the purpose of a distribution test to refuse to install because it can't test its POD. Hooray, your module that depends on Test::POD gets a perfect phalanx score. Boo, it cost me an extra twenty minutes to install it.

    update Note that I am not recommending that you don't use Test::POD in your test, only that you don't require it for installation.

[reply]
      I agree 100%. That's why the sample 4-line code that I suggest people use as t/pod.t does that exclusion.

      xoxo,
      Andy

[reply]
        Um, where? I can't find your "4-line code". Thanks.
[reply]

In Section Meditations