I vote No, for most of the same reasons already posted by chromatic.
I like Test::NoWarnings. Its author, Fergal Daly, is one of the sharpest people in the Perl QA world. But Test::Warnings is not part of the Perl core distribution. So to earn this proposed Kwalitee metric, I would have to include Test::NoWarnings underneath the t/ directory in each one of my CPAN distributions. That's pointless.
You're kidding, right? (Score:1)
I don't have any sympathy for the "uses_test_nowarnings" metric (mainly because it promotes Test::NoWarnings to a universal best practice to be used -- and abused -- everywhere). That happened before with Test::Pod and Test::PodCoverage and their corresponding metrics. On the other hand, to make sure that your code is free from warnings you don't know about is a good idea. But there's code that needs it and others that don't -- just like it happens with "use warnings" or "use strict".
But you're certainl
Re: (Score:1)
Refusing to add unnecessary complexity which only serves to toggle one bit in a Kwalitee index is a sure sign of Actual Quality. This is one case where Kwalitee is very much at odds with Quality.