# New Ticket Created by Jerry Gay # Please include the string: [perl #40596] # in the subject line of all future correspondence about this issue. # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40596 >
modify perl coding standard test format to match the c tests--one test per standard, rather than one test per file. coding standard tests are designed to test maintainability, not functionality. testing parrot functionality is much more important than testing maintainability--just look at perl 5 :-) inflating test numbers (and percentages) by adding a zillion coding standards tests leads to false perception of test coverage. i'd like very much to avoid this situation. ~jerry
