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
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Test::Unit is dead. Long live the Test::Unit::Lite (Score:1)
Re: (Score:2)
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.
Re: (Score:1)
Re: (Score:2)
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.
Re: (Score:1)
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
Re:Test::Unit is dead. Long live the Test::Unit::L (Score:1)
Assertion numbers are like version numbers: they're meaningless except insofar as they're different from each other.
Reply to This
Parent