I have some legacy tests being run with a homegrown test-runner which is calling do t/test.t on each. It works all right as set-up but I want to add some new tests which require development library paths and I'd like to have that code in the test-runner once instead of the tests dozens of times.

Anything that would work -- within the current setup; I don't think I could use App::Prove for example -- would be appreciated greatly, even if messy/hacky (the only solution I can see after messing with it is to slurp the test, prepend some "use lib" stuff and then eval it). Getting more tests going is important and the runner will probably be jettisoned some day while the tests ought to be mostly salvageable.