Bug #129271 for Papery: Test suite fails if Pod::POM is not installed

Mon Apr 22 05:13:38 2019 SREZIC [...] cpan.org - Ticket created

Subject:

Test suite fails if Pod::POM is not installed

t/30-pod-pom.t is correctly skipped: ... t/30-pod-pom.t .... skipped: Can't load Papery::Processor::Pod::POM ... But t/pod-coverage.t fails if Pod::POM is missing: ... # Failed test 'Pod coverage on Papery::Processor::Pod::POM' # at /usr/perl5.28.1Dp/lib/site_perl/5.28.1/Test/Pod/Coverage.pm line 133. # Papery::Processor::Pod::POM: requiring 'Papery::Processor::Pod::POM' failed # Looks like you failed 1 test of 8. t/pod-coverage.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/8 subtests ...

Mon Apr 22 12:20:56 2019 ether [...] cpan.org - Correspondence added

On 2019-04-22 02:13:38, SREZIC wrote: Show quoted text

> t/30-pod-pom.t is correctly skipped: > > ... > t/30-pod-pom.t .... skipped: Can't load Papery::Processor::Pod::POM > ... > > But t/pod-coverage.t fails if Pod::POM is missing:

While this test failure is indeed an issue that should be corrected, please don't allow pod, critic, coverage 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, neither of which can be predicted in advance. Either move these tests to xt/, or guard them with: plan skip_all => "These tests are for authors only!" unless $ENV{AUTHOR_TESTING} or $ENV{RELEASE_TESTING};

Mon Apr 22 12:20:56 2019 The RT System itself - Status changed from 'new' to 'open'