On Tue, Mar 08, 2005 at 03:31:37PM +0000, Mark Stosberg wrote:
> Right now the tests are run one at a time, losing the benefit
> of the summary report.
>
> I got stuck trying to think of how to best make this work.
>
> I don't think I want to use 'Makefile.PL', because the project already
> has it's own 'make' file. I would also just like to avoid 'make',
> because it's another tool to learn and complicate things.
>
> I suspect I might be overlooking a simple way to do this.
perl -MTest::Harness -e 'runtests @ARGV' tests/*.pl
> I thought of distributing a private copy of Test::Harness with the
> tests, but I thought there should be a lighter weight or more elegant
> solution.
Why would you distribute a private copy of Test::Harness? It comes with
Perl. Or do you mean you want to run the shell scripts, too? I'd make life
simpler and dump the shell scripts, see the note about cross-platform
compatibility below.
Otherwise you can replace $Test::Harness::Strap with your own instance of a
Test::Harness::Straps subclass which overrides analyze_file() to deal with
shell scripts as well as Perl.
PS I took a look at one of the Perl tests (pull.pl) and its needlessly
Unix-centric making lots of shell calls which can easily be done with
Perl, particularly rm -rf and mkdir -p (File::Path). Best to make it
cross-platform as early as possible, it sucks to bolt it on later.
PPS You're suspiciously lacking in a README or INSTALL document. I know
its probably buried somewhere in the manual/ directory but still its the
first place many people look.
