In my last steps to become a "real tester" I've been throwing in some POD tests to make sure I have all my subs documented. Test::Pod::Coverage is of course the tool of choice, but I think I'm misusing  all_pod_coverage_ok (or  all_modules.

I'm not trying to test a distribution (in the strictest sense of the word), but I am trying to test a collection of database-interaction modules.

my first thought, since this isn't a packaged dist, was to use  all_modules( $dir );, but that gives me: 

[me@2 t]$ prove -v 900_pod_coverage.t
900_pod_coverage....Undefined subroutine &main::all_modules called at 
+900_pod_coverage.t line 9.

[download]
but the code is very straightforward, or so i thought: 
# -*- perl -*-

# t/900_pod_coverage.t - check POD coverage for new modules

use Test::Pod::Coverage; # tests => 1;

use lib qw# /home/httpd/path/to/my/plugins/ #;
my $dir = q{/home/httpd/path/to/my/plugins/};

## also tried the commented out ... 
# my @moduleList =  all_modules( 'DataClasses' );
my @moduleList =  all_modules( $dir );

foreach my $mod ( @moduleList ) {

 pod_coverage_ok( $mod, 'reporting code is documented' );

}

[download]
I must be missing something obvious. Sure, I could switch over to something like readdir() ... At this point, I want to know if I'm way of the path of the module's intentions, since the perldoc isn't too descriptive.

In reply to Test::Pod::Coverage and all_pod_coverage_ok by geektron

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.