in reply to Order of startup methods with Test::Class
This is a common anti-pattern I see in Test::Class code. If you have a subclass, you should view this as a more specific instance of your parent class. Your startup/setup/teardown/shutdown methods (which I refer to as "test control methods") shouldn't rely on a prefix hack, as you rightly pointed out. Instead, you override them and your subclass calls the parent class's method as appropriate:
sub setup : Tests(setup) { my $test = shift; $test->SUPER::setup; # my setup code here }
With this approach, you have complete control over the order of how things run and you don't have to worry about prefixes.
You might want to read my tutorial on Test::Class, in particular the test control methods section.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: Order of startup methods with Test::Class
by chrestomanci (Priest) on Oct 09, 2011 at 20:21 UTC | |
by Ovid (Cardinal) on Oct 10, 2011 at 19:30 UTC |
In Section
Seekers of Perl Wisdom