POD coverage testing is easier

petdance on 2004-02-14T05:31:34

I just released Test::Pod::Coverage 0.08, so that you don't have to specify the module names for your distribution.

use Test::More; eval "use Test::Pod::Coverage 0.08"; plan skip_all => "Test::Pod::Coverage 0.08 required for testing POD coverage" if $@; all_pod_coverage_ok();

---

0.08

jonasbn on 2004-02-14T09:25:57

Now I have changed my pod_coverage.t to follow the test you outline, so now I just have to wait for Test::Pod::Coverage 0.08 at my local CPAN mirror.

Keep up the good work,

jonasbn

Re:0.08

petdance on 2004-02-14T15:19:26

It's now there on http://search.cpan.org/dist/Test-Pod-Coverage/

The big win for me is not having to remember to change the module names as I cut and paste my t/pod-coverage.t file around. I had one module where I'd cut'n'pasted the t/pod-coverage.t from WWW::Mechanize, but it was still referring to WWW::Mechanize and WWW::Mechanize::Link. It always worked for me, regardless of how bad the docs in the module were.

Now that I think about it, I need to make sure that it ONLY looks in blib.

Bah!

Adrian on 2004-02-14T10:46:18

I was going to do that for that as next weeks resolution item - now I have find something else useful to do you swine :-)

Good stuff. Yet more large number of lines to be removed from a few test scripts.