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

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

This is the sort of crap that "patch" test reports cause... 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Your argument may or may not have merit, but PDF::API2 is a terrible example to make your point.

    Have you looked in the t/ directory of PDF::API2? Here, I'll save you the time:

    use Test;
    BEGIN { plan tests => 1 }
    use PDF::API2; ok(1);

    With no unit tests, a PASS is meaningless. Only a FAIL has any meaning at all.

    That said, I think PDF::API2 is good code and Fredo has been remarkably responsive in my experience, but my own not-really-competing CAM::PDF [cpan.org] library has unit tests with code coverage over 50% --

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.