Bug #112922 for Log-Fine: pod coverage test may fail

Fri Mar 11 02:11:21 2016 SREZIC [...] cpan.org - Ticket created

Subject:

pod coverage test may fail

Test output looks like this: # Failed test 'Pod coverage on Log::Fine::Handle::Email' # at /opt/perl-5.22.0t/lib/site_perl/5.22.0/Test/Pod/Coverage.pm line 133. # Log::Fine::Handle::Email: requiring 'Log::Fine::Handle::Email' failed # Looks like you failed 1 test of 19. t/pod-coverage.t ............... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/19 subtests I think the problem happens because the (optional) prereqs for Log::Fine::Handle::Email are not met in this case. Probably testing this module for pod coverage should be skipped in the same cases like it's done in t/15-handle-email.t.

Fri Mar 11 13:09:01 2016 ether [...] cpan.org - Correspondence added

On 2016-03-10 23:11:21, SREZIC wrote: Show quoted text

> Test output looks like this: > > # Failed test 'Pod coverage on Log::Fine::Handle::Email' > # at /opt/perl-5.22.0t/lib/site_perl/5.22.0/Test/Pod/Coverage.pm > line 133. > # Log::Fine::Handle::Email: requiring 'Log::Fine::Handle::Email' > failed > # Looks like you failed 1 test of 19. > t/pod-coverage.t ............... > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/19 subtests > > I think the problem happens because the (optional) prereqs for > Log::Fine::Handle::Email are not met in this case. Probably testing > this module for pod coverage should be skipped in the same cases like > it's done in t/15-handle-email.t.

Please don't allow pod, critic or kwalitee tests to run for normal user installs, as they make the installation fail unnecessarily when newer versions of the tester module introduces errors that you cannot anticipate. Also spelling tests are dependent on what dictionaries are installed locally, and critic tests use all plugins that are installed, both of which cannot be predicted in advance. Either move them to xt/, or guard them with: plan skip_all => "These tests are for authors only!" unless $ENV{AUTHOR_TESTING} or $ENV{RELEASE_TESTING};

Fri Mar 11 13:09:02 2016 The RT System itself - Status changed from 'new' to 'open'