Slash Boxes
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 ]

ajt (2546)

  (email not shown publicly)

UK based. Perl, XML/HTTP, SAP, Debian hacker.

  • PerlMonks: ajt []
  • Local LUG: AdamTrickett []
  • Debian Administration: ajt []
  • LinkedIn: drajt []

Journal of ajt (2546)

Thursday January 25, 2007
05:17 PM

Code Test Coverage

[ #32255 ]

This week I've been working on my XML::RSS::Tools module at home and on some SAP ABAP development at work. At work within SAP I don't have the luxury of a nice testing environment and code coverage tools that I use to at home for Perl.

I know Perl better than ABAP, so I think it's fair to say that my Perl code is better than my ABAP. What amazes me is how poor code can be unless you really analyse it properly, even when you think it's good. I've been using Test::Cover and the PBP guidelines to improved XML::RSS::Tools, it's my oldest module, and the test coverage is quite puny - though getting better.

Ironically I spotted this today on El Reg: Teaching an Old Dog New Tricks, quite appropriate timing I thought.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • It was an interesting article, though it degenerated into an advertisement for the security checker by the end.

    At least that's what I thought, but wasn't sure. So kept on reading.

    I think I liked the insights about what you learn from learning how to program. What's the take-home learning.
    • I agree it's a bit of an advert, but it's also interesting to see someone admit that code they thought they had written well, wasn't!

      -- "It's not magic, it's work..."