good chemistry is complicated, and a little bit messy -LW |
|
PerlMonks |
Re: Test the Pod of your filesby adrianh (Chancellor) |
on Jan 06, 2003 at 17:58 UTC ( [id://224678]=note: print w/replies, xml ) | Need Help?? |
If you want something completely general you should check under blib rather than lib, since the Makefile.PL could run a filter on the source (not really an issue if you don't do that - but you never know :-). It also might be easier to just base it on Test::Builder instead of pulling in Test:More. You might want to take a glance at pod.t and documented.t (part of the tests for Test::Class and Test::Exception) written before Test::Pod was around. They're a little hacky but seem to work a fair number of places (see http://testers.cpan.org/ for the full list). pod.t does basically what Test::Pod does, but searches for all modules in the specified directories, rather than being given an explicit list. documented.t uses Pod::Coverage to check that the POD actually documents the code in the module. Again, it searches for modules rather than being given an explicit list.
In Section
Cool Uses for Perl
|
|