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.
  • Please. some people just want to use real OO test suite, not just poor Test::Simple.
    • Test::Class is the way to go here. It also integrates with all of the standard Perl testing libraries. It doesn't look like Test::Unit::Lite does that.

      • Standard Perl testing libraries have poor and ugly non-OO API. Theirs tests also don't die after failure which differs from JUnit, PerlUnit, etc.
        • I should also add that if you really want to march to a different drummer and use a piece of software that virtually no one else will touch, that's fine, but at least see if you can submit patches to it so that it can at least output TAP and integrate with standard testing tools.

          • Well, yes. It means that the standard testing tool are really TAP protocol and Test::Harness module, not Test::Simple or Test::More.

            BTW, I'd like to see support for nested tests for TAP protocol, something like:
            1..3
            unit 1..2
            ok PASS unit 1/1
            ok PASS unit 1/2
            unit 1..1
            ok PASS unit 2/1
            unit 1..3
            ok PASS unit 3/1
            not ok Something goes wrong with 3/2
            ok PASS unit 3/3

            It is sad that the JUnit model really can't be implemented with Perl's TAP because TAP protocol