Re: Order of startup methods with Test::Class

[Ovid]

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.

[chrestomanci]

Ovid++

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.

[Ovid]

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.