Hi there.
Some modules uses Test::Perl::Critic tests outside of author environment, that can result in FAIL because some installed
Perl::Critic::Policy'ies are violated. Once I've seen a policy that contradicts to one of default policies, leading test
to failure every time when policy subject is triggered no matter how code is written.
I'm thinking to have something like Perl::Critic::Policy::TestingAndDebugging::AlwaysFail installed in smoker
environment, which reports P::C violation every time it is called. It would discourage CPAN authors from providing tests
that have nothing with module functionality. LWP::Useragent, DBI, DBD::SQLite, CPAN.pm and thousands other modules would
fail "perlcritic" even on level 5, but it doesn't mean they don't work.
What do you think about it?
--
Serguei Trouchelle
