The trick is to return from the INIT
routine, which will put you at the first executable line of your test. In the debugger, that's an r
commamd. Maybe "step out" in Eclipse?
You should then set any breakpoints you want in the specific test subs then c to continue (or whatever Eclipse's equivalent of "run from here to the next breakpoint" is). Otherwise be prepared to step your way through a lot of code you don't care about until you reach the call that actually executes your code somewhere in the bowels of Test::Class.