On Sun Oct 03 12:13:22 2010, ANDK wrote:
Show quoted text> As per subject.
>
> Example of a failing test report:
>
>
http://www.cpantesters.org/cpan/report/8601178
>
> I believe Test::Perl::Critic tests should be author tests because they
> may uncover bugs but they may also just uncover violations of principles
> that are not critical (sic!).
Hi, 4.0 was a pretty heavy change-set and I've found enabling the tests
on cpan testers to be invaluable. I'd rather leave them enabled ATM and
fix issues as they arise.
I already excluded ProhibitAccessOfPrivateData which was giving bogus
results.
In this case the test checks the module for which perl to use, but not
any restrictions in the Build or Makefiles, perhaps there are other
places this is also true. I think it's best to duplicate the use from
the Build file in Parse.pm.
http://github.com/jfearn/HTML-Tree/commit/457efcf65b51fabf42492a8d6e335b2d14d7101a
Tests fine with Perl-Critic-Compatibility installed now.
Thanks for the report!
Cheers, Jeff.