Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

ChrisDolan (2855)

ChrisDolan
  (email not shown publicly)
http://www.chrisdolan.net/

Journal of ChrisDolan (2855)

Thursday August 17, 2006
10:46 AM

Perl::Critic test coverage

[ #30671 ]

I'm one of the seven core developers for the Perl::Critic package.

I spent a bunch of time this week rounding out the test coverage. When I started Monday, we were already over 90% coverage, according to Devel::Cover. Now we're over 95% with a couple fewer bugs than before. I'm happy to say that MOST of our 80 policy modules now have 100% test coverage. While coverage does not map directly to software quality, of course, it's one of the best metrics available so I'm pretty proud of our accomplishments.

We're working toward a 1.0 release sometime early this fall.


List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Perl::Critic test coverage 9 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I use P::C all the time.
    • Great! Have any features you'd like added? Any additional policies you'd like to see enforced?

      Our TODO.pod is big already, but I'd love to add more good ideas to it.
      • I have a minor nit/suggestion. In the pod/docs for each policy, it would be nice if it mentioned the default severity level for each policy module.

        I found myself viewing source on every module trying to fine out which severity level it applied to.

        In the end, I ended up setting my test file to severity = 1, and then making a policy for each dist that customized or disabled the policies that didn't jive w/ the dist. Kind of a All On By Default thing. Then when new policies come out, I'll automaticaly catch th
        • I recommend "bin/perlcritic -list" which lists all of the policies by package name and severity.

          On the developer mail list, we're discussing transforming the severity system into a more generic tagging system. My hope is that we'll implement that for v1.0 within the next month.
      • Also, I think Variables::ProhibitPunctuationVars should be tweakable imho.

        I agree with most of it, but I'd like ti be able to tell it to except $@ as well.
        • Your wish is my command. :-)

          I just committed a patch to SVN that implements the following example:

              [Variables::ProhibitPunctuationVars]
              allow = $@ $!

          This feature will be present in the forthcoming v0.19.
  • I curse you and your Perl:Critic post! I was coding along, getting things done, then I had to read this post and install [Test::]Perl::Critic and make a test script for my dists. Holy distraction batman. :-)
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.