On 2/8/07, Christopher H. Laco <[EMAIL PROTECTED]> wrote:
Nik Clayton wrote: > Paul Johnson wrote: >> On Thu, Feb 08, 2007 at 09:26:01AM +0000, Nik Clayton wrote: >> >>> [ I vaguely recall a discussion about this, but my search-fu is weak, >>> and I can't find it ] >>> >>> Is there a standard way/idiom to get ExtUtils::MakeMaker to support >>> tests in subdirectories of t/? >>> >>> I've got a bunch of tests, and rather than client-ls.t, client-add.t, >>> client-commit.t, etc, I'd like t/client/ls.t, t/client/add.t, >>> t/client/commit.t, and so on. >> >> I have this in one of my Makefile.PLs, which seems to be just about >> what you >> are looking for: >> >> WriteMakefile >> ( >> ... >> test => { TESTS => "t/*/*.t" }, >> ... >> ); > > Ah. My mistake for not being clear enough. I want to run t/*.t and > t/*/*.t. > > Of course, I tried > > test => { TESTS => [ "t/*.t", "t/*/*.t" ] }, > > and it doesn't work. It's just occurred to me that I'm trying to be too > clever. > > test => { TESTS => "t/*.t t/*/*.t" }, > > works perfectly. > > N > >I offer this word of warning. If you have too many tests, or many longly-named tests, win32 will in all likelyhood barf with a command line too long error.
I think this is a legitimate issue to consider. What particular sequence of events leads to this happening and how can we address it. The other thing that comes to mind is making the tree too deep, such that on win32 you exceed the maximum path length. I guess other platforms have similar but different zaps and traps to consider as well. cheers, Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"
