runprove [options] [files/directories]
-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 runprove -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 --timer Print elapsed time after each test file -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.
runprove is a command-line interface to the test-running functionality of
Test::Run. With no arguments, it will run all tests in the current directory.
Shell metacharacters may be used with command lines options and will be exanded via
Runprove vs. “Make Test”
runprove has a number of advantages over
make test when doing development.
runprove is designed as a development tool
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.
runprove is granular
runprove let your run only the files you want to check. Running
runprove t/live/ t/master.tchecks every *.t in t/live, plus t/master.t.
prove has an easy verbose mode
runprove has a
-voption to see the raw output from the tests. To do this with
make test, you must set
HARNESS_VERBOSE=1in the environment.
runprove can run under taint mode
runprove can shuffle tests
You can use runprove's
--shuffleoption to try to excite problems that don't show up when tests are run in the same order every time.
runprove doesn't rely on a make tool
Not everyone wants to write a makefile, or use ExtUtils::MakeMaker to do so. runprove has no external dependencies.
Not everything is a module
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.
Command Line Options
Adds blib/lib to the path for your tests, a la “use blib”.
Include debug information about how runprove is being run. This option doesn't show the output from the test scripts. That's handled by -v,--verbose.
Dry run: Show the tests to run, but don't run them.
Specify extensions of the test files to run. By default, these are .t, but you may have other non-.t test files, most likely .sh shell scripts. The --ext is repeatable.
Add libraries to
@INC, as Perl's -I.
@INC. Equivalent to
Descends into subdirectories of any directories specified, looking for tests.
Sometimes tests are accidentally dependent on tests that have been run before. This switch will shuffle the tests to be run prior to running them, thus ensuring that hidden dependencies in the test order are likely to be revealed. The author hopes the run the algorithm on the preceding sentence to see if he can produce something slightly less awkward.
Runs test programs under perl's -t taint warning mode.
Runs test programs under perl's -t taint mode.
Print elapsed time after each test file
Display standard output of test scripts while running them. Also sets TEST_VERBOSE in case your tests rely on them.
Display version info.
Please report any bugs or feature requests to
email@example.com, or through the web interface at <http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Test-Run-CmdLine>. I will be notified, and then you'll automatically be notified of progress on your bug as I make changes.
- Shuffled tests must be recreatable
<firstname.lastname@example.org> (Adapted to runprove by Shlomi Fish, <http://www.shlomifish.org/> ).
Copyright 2005 by Andy Lester
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.