On 2013-11-06 07:55:42, FERREIRA wrote:
Show quoted text> On Mon Jul 29 20:20:23 2013, ETHER wrote:
> > Pod tests should only be run by the author, and therefore protected
> > with a guard checking for an %ENV variable so they don't run at
> > install time.
>
>
> Solved with
https://github.com/aferreira/cpan-Carp-
> Always/commit/47a09038f72abc5d3062d02a2e444fd413b27592
reopening, as this is still an issue:
The tests will continue to run at install time the same as they did before:
https://metacpan.org/source/FERREIRA/Carp-Always-0.13/t/098pod-coverage.t
You need to either move the tests themselves out of t/ to somewhere like xt/, or put a guard at the top of the code so they are skipped when $ENV{AUTHOR_TESTING} is not set.
The problem occurs when the pod parser starts emitting a new warning (as it recently did when encountering non-ASCII characters without an explicit =encoding directive) which makes the module uninstallable (without forcing) for users who happen to have Test::Pod installed.
And, as it is now, the tests will be skipped if the author shipping the dist doesn't have the modules. That makes it far too easy to ship a new release that would fail the pod tests without noticing it.
RT for rt.cpan.org