----- Original Message ---- > From: Matisse Enzer <[EMAIL PROTECTED]>
> I organize my test files using an approach similar to nUnit - I > create > a bunch of subroutines that each do a few assertions, and that call > set_up() and tear_down(). ... > sub test_foo { > my $foo = set_up(); > # do some assertions using $foo > return tear_down($foo); > } > > sub test_bar { > my $foo = set_up(); > # do some assertions using $foo > return tear_down($foo); > } > > sub test_baz { > my $foo = set_up(); > # do some assertions using $foo > return tear_down($foo); > } You know, all of those set_up() and tear_down() calls are repetitive and can be factored out. Test::Class does that for you for free :) Cheers, Ovid -- Buy the book - http://www.oreilly.com/catalog/perlhks/ Perl and CGI - http://users.easystreet.com/ovid/cgi_course/ Personal blog - http://publius-ovidius.livejournal.com/ Tech blog - http://use.perl.org/~Ovid/journal/