Subject: | Suggestion: Trick quality for Test::Pod etc dependencies |
Hi Apocalypse:
I noticed in your test suite for Test::Apocalypse, in t/a_apocalypse.t,
you've got:
require Test::NoWarnings; require Test::Pod; require
Test::Pod::Coverage; # lousy hack for kwalitee
I came across this issue myself. You can hack around the Kwalitee
detection by using:
0 and require Test::NoWarnings;
This way you don't actually require it (it can be used optionally via
eval as per the recommended usage), though I'm not sure if you'd rather
those modules always be available whenever a module tests against
Test::Apocalypse.
Also, you may want to differentiate between AUTOMATED_TESTING and
RELEASE_TESTING (rather than simply the TEST_AUTHOR env var from the old
days). The reasons why are discussed by Alias in his blog, here:
http://use.perl.org/~Alias/journal/38822
Cheers,
Jonathan