We have this ticket in the Test::Harness RT queue: http://rt.cpan.org/Ticket/Display.html?id=29633
Martin Thurn is asking for a SKIP_OUT directive that would skip all remaining test files and return a PASS.
I don't like that idea; it depends on the order of execution of test scripts and it's a lot of hassle for what is probably a fairly unusual case.
But what about a more general mechanism? A TAP directive that means 'schedule these other tests'. So then you'd have a controller test which was the only one directly visible to Test::Harness and that'd decide which other tests to run. And of course that'd be recursive - so nested controllers could implement selective execution of huge test suites.
-- Andy Armstrong, Hexten
