Why haven't you done what I suggested?

I tried it at first but ran into problems and gave up.

After some further examination I realized that the key to getting it working was to just drop in the test.pl and rename the "t/" directory, but NOT add the test => { TESTS => 'test.pl' } part to the Makefile.PL.

I integrated this with a few other suggestions from chromatic and BrowserUK to come up with the following, which seems to work well under Unix, and I'm hopeful that it'll also solve my Win32 issues. 

#!perl

use Test::Harness;
use File::Find;

# Use both glob() and find() to locate all target .t files across plat
+forms

@tdirs = ( ! @ARGV ) ? '.' : map ( glob(), @ARGV ) 
    or die "test.pl: Can't find any tests matching @ARGV\n";

find( sub { /\.t\z/ and push @tests, $File::Find::name }, @tdirs );

@tests = sort { lc $a cmp lc $b } @tests 
    or die "test.pl: Can't find any tests in @tdirs\n";

# Run the tests, using code from ExtUtils::testlib and ExtUtils::Comma
+nd::MM

unshift @INC, qw( blib/arch blib/lib );
$Test::Harness::verbose = $ENV{TEST_VERBOSE} || 0;
Test::Harness::runtests( @tests );

__END__

=head1 NAME

test.pl - Test harness with recursive directory search

=head1 SUMMARY

  make test

  perl test.pl

  perl test.pl [DIRECTORY|FILENAME|FILEGLOB]*

=head1 DESCRIPTION

Performs a recursive directory search for files ending in C<.t>,
starting from the current directory or from the paths specified on
the command line, and then runs them using Test::Harness.

=head1 CAUTION

This is a test harness, not a test script.

MakeMaker checks for the presence of a test harness named test.pl
and if present adds code to the test target to run it. Do NOT add
this to the test scripts used by a Makefile.PL (using C<test => {
TESTS => 'test.pl' }>). Do NOT create a directory named C<t/> or
else MakeMaker will also attempt to run those test scripts itself.

=head1 CREDITS AND COPYRIGHT

=head2 Author

Developed by Matthew Simon Cavalletto at Evolution Softworks. 
More free Perl software is available at C<www.evoscript.org>.

You may contact the author directly at C<evo@cpan.org> or C<simonm@cav
+alletto.org>. 

=head2 Thanks To

Developed with the assistance of the Perl Monks community; my thanks 
in particular to PodMaster, chromatic, BrowserUk, and Murat.

=head2 Copyright

Copyright 2004 Matthew Simon Cavalletto. 

=head2 License

You may use, modify, and distribute this software under the same terms
+ as Perl.

=cut

[download]

Thanks for everyone's help with this; feedback on this code or any additional suggestions would be welcome.

In reply to Re^2: Too many tests for Windows command line? by simonm
in thread Too many tests for Windows command line? by simonm

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.