This feels very X-Unity. He might want to look at Test::Class which provides very similar functionality. Dedicated, inherited test methods. Setup/teardown routines.
The major benefits of a changeover include no longer having to maintain your own X-Unit module, parsable output, being able to play with all the other Test::Builder derived modules and Perlish testing functions (ie. is() instead of assert_eq()). Since he's coming from an X-Unit background, the idea that the test and the harness are different things might take a little getting used to. To ease the transition, it should be pretty trivial to rewrite your system as a subclass of Test::Class and also to reimplement your assert functions using Test::Builder. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/ Thanks, applied. Or, [EMAIL PROTECTED] as we Bulgarian EBCDIC users like to say. -- Jarkko Hietaniemi in <[EMAIL PROTECTED]>
