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.
        • "Standard Perl testing libraries have poor and ugly non-OO API"

          "Standard" perl testing libraries are organisationally agnostic. Which is one of their great advantages. So you can write OO (if you want) with things like Test::Class, or procedurally (if you want) with plain Test::More style, or in a functional style, or... whatever...

          Please go look at Test::Class - which has a very OO API :-)

          "Theirs tests also don't die after failure which differs from JUnit, PerlUnit, etc"

          It does differ from jUnit - not entirely sure if it's always a clear cut win however. there are sometimes advantages to seeing all of the assertion failures in a test. Depends how you write your test methods.

          It's also trivial to make them error on initial failure if you want them to.