diff options
author | Steve Hay <steve.m.hay@googlemail.com> | 2013-10-11 11:21:27 +0100 |
---|---|---|
committer | Steve Hay <steve.m.hay@googlemail.com> | 2013-10-11 11:21:27 +0100 |
commit | befb53592411375e6f3fb664447f4f80067211e1 (patch) | |
tree | da0b70e9685d66404c02a91469c38edc669c5c77 /cpan/Test-Harness/bin/prove | |
parent | 56583f24b228f2aa9022b2d2ba102c43e5159482 (diff) | |
download | perl-befb53592411375e6f3fb664447f4f80067211e1.tar.gz |
Upgrade Test::Harness from version 3.28 to 3.29
This includes the blead CUSTOMIZATION of t/source.t.
Diffstat (limited to 'cpan/Test-Harness/bin/prove')
-rw-r--r-- | cpan/Test-Harness/bin/prove | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/cpan/Test-Harness/bin/prove b/cpan/Test-Harness/bin/prove index 4f46ed6598..46b0453163 100644 --- a/cpan/Test-Harness/bin/prove +++ b/cpan/Test-Harness/bin/prove @@ -1,6 +1,7 @@ #!/usr/bin/perl -w use strict; +use warnings; use App::Prove; my $app = App::Prove->new; @@ -272,7 +273,7 @@ which are run in parallel, if the C<--jobs> option is specified. The option may be specified multiple times, and the order matters. The most practical use is likely to specify that some tests are not -"parallel-ready". Since mentioning a file with --rules doens't cause it to +"parallel-ready". Since mentioning a file with --rules doesn't cause it to selected to run as a test, you can "set and forget" some rules preferences in your .proverc file. Then you'll be able to take maximum advantage of the performance benefits of parallel testing, while some exceptions are still run @@ -288,7 +289,7 @@ in parallel. =head3 --rules resolution -=over4 +=over 4 =item * By default, all tests are eligible to be run in parallel. Specifying any of your own rules removes this one. |