[Omaha.pm] best practice: podchecker
Jay Hannah
jhannah at omnihotels.com
Thu Jul 21 15:10:49 PDT 2005
From: Andy Lester <andy at petdance.com>
> > If your work has a test suite with it, you can also use the standard
> > t/pod.t. Here's one from WWW::Mechanize:
> >
> > http://search.cpan.org/src/PETDANCE/WWW-Mechanize-1.13_01/t/pod.t
Sweet... After 30m correcting 30 some classes w/ POD glitches we now have another 1,404 tests in our test suite.
> perl -e 'use Test::Harness; undef $Test::Harness::switches; runtests(@ARGV)' t/pod.t
t/pod....ok
All tests successful.
Files=1, Tests=1404, 3 wallclock secs ( 2.46 cusr + 0.19 csys = 2.65 CPU)
Nothing like padding your test suite stats. -grin-
Probably helped my big pod2html dump on our Intranet too.
j
More information about the Omaha-pm
mailing list