> I don't know what you mean by "using prove"?
prove is a command-line utility that ships with Test::Harness. It
allows you to run a specific test or tests, as specified on the command
line, without having to go through the make test rigamarole. Example:
prove -Mblib -v t/dataconnect.t t/dbi/*.t
In fact, one of the swell things that prove does is runs tests in a
random order, to potentially excite any bugs that remain hidden because
of the specific order in which they're always run.
Here's the usage on it:
$ prove -h
Usage:
prove [options] [files/directories]
Options:
-b, --blib Adds blib/lib to the path for your tests, a la
"use blib".
-d, --debug Includes extra debugging information.
-D, --dry Dry run: Show the tests to run, but don't run them.
--ext=x Extensions (defaults to .t)
-h, --help Display this help
-H, --man Longer manpage for prove
-I Add libraries to @INC, as Perl's -I
-l, --lib Add lib to the path for your tests.
-r, --recurse Recursively descend into directories.
-s, --shuffle Run the tests in a random order.
-T Enable tainting checks
-t Enable tainting warnings
-v, --verbose Display standard output of test scripts while
running them.
-V, --version Display version info
Single-character options may be stacked. Default options may be set by
specifying the PROVE_SWITCHES environment variable.
Prove is a genericized version of the testing script that we've been
using in my department for the past couple of years. It's completely
changed the way we write code.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
