Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things

Re: Order of startup methods with Test::Class

by Ovid (Cardinal)
on Oct 09, 2011 at 15:02 UTC ( #930476=note: print w/replies, xml ) Need Help??

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


    Thank you, that was the answer I was looking for.

    All I have to do is name all my setup methods the same, and subclass where appropriate.

      Happy to have helped. By the way, I noticed you're using my Test::Most module. Since you're also using Test::Class, you might also find my Test::Class::Most module handy.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://930476]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others imbibing at the Monastery: (6)
As of 2018-06-21 12:39 GMT
Find Nodes?
    Voting Booth?
    Should cpanminus be part of the standard Perl release?

    Results (118 votes). Check out past polls.