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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Last I checked, Test::Builder was pretty much at the center of testing, and as far as I'm concerned, pretty much all functionality possible should be there.

    Just to get really wild, I don't know a whole lot about how all the various parts of testing interact, so I'm looking at it with a clean (and probably ignorant slate), and I wonder if there should even be a harness.....

    --
    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
    • Well, the problem with that is that TAP is the Test Anything Protocol, which is to say you don’t know if the tests on the other end of the harness use Test::Builder, or if they are written in Perl in the first place, or even if they run on something that has a microprocessor at all – for all you know, you’re parsing the self-test output of an embedded device received over a serial port. So the “harness should be responsible” camp has a point.

      On the other hand (which is the ar