Bug #117419 for UTM5-URFAClient: pod coverage and pod tests fail

Thu Sep 01 17:35:54 2016 SREZIC [...] cpan.org - Ticket created

Subject:

pod coverage and pod tests fail

# Failed test 'POD test for blib/lib/UTM5/URFAClient.pm' # at /opt/perl-5.24.1-RC3/lib/site_perl/5.24.1/Test/Pod.pm line 187. # blib/lib/UTM5/URFAClient.pm (60): '=item' outside of any '=over' # Looks like you failed 1 test of 1. t/07-pod.t ............ Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests # Failed test 'Pod coverage on UTM5::URFAClient' # at /opt/perl-5.24.1-RC3/lib/site_perl/5.24.1/Test/Pod/Coverage.pm line 133. # Coverage for UTM5::URFAClient is 94.7%, with 1 naked subroutine: # users_list # Looks like you failed 1 test of 1. t/08-pod-coverage.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests

Fri Sep 02 12:43:57 2016 ether [...] cpan.org - Correspondence added

On 2016-09-01 14:35:54, SREZIC wrote: Show quoted text

> # Failed test 'POD test for blib/lib/UTM5/URFAClient.pm' > # at /opt/perl-5.24.1-RC3/lib/site_perl/5.24.1/Test/Pod.pm line 187. > # blib/lib/UTM5/URFAClient.pm (60): '=item' outside of any '=over' > # Looks like you failed 1 test of 1. > t/07-pod.t ............ > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/1 subtests > > # Failed test 'Pod coverage on UTM5::URFAClient' > # at /opt/perl-5.24.1-RC3/lib/site_perl/5.24.1/Test/Pod/Coverage.pm > line 133. > # Coverage for UTM5::URFAClient is 94.7%, with 1 naked subroutine: > # users_list > # Looks like you failed 1 test of 1. > t/08-pod-coverage.t ... > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/1 subtests

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};

Fri Sep 02 12:43:57 2016 The RT System itself - Status changed from 'new' to 'open'