Does the fact that it neglects to base it itself on Test::Builder mean that it does not play nicely with the stadard testing phase of CPAN style module distributions?
Yes and no.
T::U can be made to output TAP (using Test::Unit::HarnessUnit) which means Test::Harness can understand it's output, so you can integrate it into the normal CPAN testing phase.
This disadvantages are that:
Well - that and the fact that its huge, overcomplicated and pretty much unmaintained :-)
If Test::Unit seemed reasonably close to what I wanted, what is the closest thing that behaves in an appropriately Perlish fashion?
Test::Class - but I would say that :-)
In reply to Re^3: Unit Testing in Perl
by adrianh
in thread Unit Testing in Perl
by skyknight
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |