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.

No PerlUnit You Fools! 5 Comments More | Login | Reply /

 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.

          How does modeling assertEquals as a static method show evidence of good design?

          • Oh, it doesn't :) It's also worth noting that Test::Unit::Lite provides virtually no diagnostic information and forces the programmer to type a heck of a lot more boilerplate with absolutely no benefit whatsoever. And we won't even talk about how incredibly primitive (read: near useless) the assertions are.

            At least with the static methods in jUnit, you don't have to type a bunch of useless $self-> statements or their equivalent (but it also means that there's no real way to track state).

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