> Err... what is the point of these? We've already got set_up and
> tear_down in the interface of Test::Unit::TestCase and I confess that
> I can't for the life of me see why you'd want to make
> Test::Unit::TestDecorator into a first class class in Perl.
Grrr. :-) Maybe I should have included the Javadoc for these classes.
I don't know if it's the best way of accomplishing what they are meant
to do, but the point of TestDecorator/TestSetup is to provide a wrapper
around a TestSuite to do common setup for all tests in the suite. This
is VERY useful for configuration operations that take a long time (such
as an install or bringing up a server).
If you have a suggestion as to how else this might be accomplished. I'd
love to hear it. The problem I have with TestSetup is communicating
state to the TestSuite it's wrapping.
-Kevin
_______________________________________________
Perlunit-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/perlunit-devel
