I have a fork of the 'testing non-modules' question. :)

I help maintain some Perl test scripts for darcs [1]. 

 1. http://www.darcs.net/

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. 

For my personal work I would use 'prove', but darcs is otherwise very
portable, and I can't expect 'prove' will be installed everywhere. 

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.

Thanks!

    Mark


Reply via email to