Test::Harness now comes with a command-line utility called prove that runs tests against the harness. Why have a separate utility? What's wrong with "make test"?
prove has a number of advantages over
make test when doing development.
Perl users typically run the test harness through a makefile via
make test. That's fine for module distributions, but it's
suboptimal for a test/code/debug development cycle.
prove lets your run against only the files you want to check.
prove t/live/ t/master.t checks every *.t in t/live,
To get full test program output from
make test, you must set
HARNESS_VERBOSE in the environment. prove has a
-T runs your tests under
You can use prove's
--shuffle option to try to excite problems
that don't show up when tests are run in the same order every time.
More and more users are using Perl's testing tools outside the context of a module distribution, and may not even use a makefile at all.
I welcome your comments and suggestions about prove, and I hope you find it as useful as I have over the past couple years of development.