> As I was downloading the newest version of Devel::Cover this morning, I > pondered on the concept of 1 Kwalitee point for coverage >= 80%, and > another for 100%, and how absolutely impossible it would be to set out > to establish these points for all the modules on CPAN. But it would be Good.
I think a point for >= 80% would be okay (for some definition of 80%). But I think a more useful measure of kwalitee would be a 20%-30% coverage test. Right now 'has_tests' is satisfied by including the default tests that module-starter provides (00.load.t, and the pod tests). There are a lot of modules that have nothing beyond the default tests and yet they get their 'has_tests' point. Passing a low coverage bar would at least indicate that the author wrote *some* tests. If there's an easier way of finding out if there are actual tests, then that would be fine too. I think there's a big difference in kwalitee between a module that has only the default tests and a module with a hand-crafted test suite. One of the first things I do when checking out a new module is to check if there are more than three files in the t/ directory. Michael --- Michael Graham <[EMAIL PROTECTED]>
