On Friday 17 August 2007 13:20:39 Eric Wilhelm wrote: > >> 1. it doesn't play nicely with recursive tests[1]
> >"It's okay to run everything in t/ recursively" is a heuristic. You > > can tell it's a heuristic because sometimes it's wrong. > That's not what I meant by "doesn't play nicely". I mean, "my project > cannot use recursive tests *and* have author-only tests in t/author > without jumping through hoops." Hoops include: a custom test action, > special options (or patches) to prove and runtests, etc. How are you getting recursive tests by default anywhere? Why you would need to patch prove or runtests? I just temporarily changed the Build.PL for Test::MockObject (which stores author-only tests in t/developer/) not to filter out that directory in the find_test_files() files method, and the developer tests still didn't run. I don't understand why you're having trouble with recursive tests, and that's maybe why I don't think this is a problem at all. I've not encountered it, and I'm curious how you have. -- c
