Skip Menu |

This queue is for tickets about the Test-Harness CPAN distribution.

Report information
The Basics
Id: 87521
Status: new
Priority: 0/
Queue: Test-Harness

Owner: Nobody in particular
Requestors: KENTNL [...]

Bug Information
Severity: (no value)
Broken in: 3.28
Fixed in: (no value)

Subject: No way to test a single file if .proverc + .prove + --state=all
There's a giant annoying thing which for me, means I can't use a .proverc in my dist:

1. add --state=fast,all,save   to your .proverc
2. prove t/*    # Works as expected
3. prove t/just_one_test.t  # re-runs the entire test suite.

That last part is a pretty seriously annoying defect, which means I can't realistically use a  .proverc file, because it essentially means I can't run a single test on its own.

Maybe, some think its "nice" that prove will run all tests, even if no tests are specified , ie:

cd $DIST ; prove # just runs all the tests

But for me, when I explicitly tell prove I want to run only certain tests, I do *NOT* expect it to run my whole test suite.

To me, --state and friends should not be governing /which/ tests run when I specify a test name, or a directory containing tests, --state and friends should only govern the ORDER of the tests.


 > prove    # do whatever , run all the tests, or some of them , thats fine
Show quoted text
> prove $PATH  # run ALL elements of $PATH , and ONLY elements of $PATH

If this is not very nice for some people, I suggest there be a parameter that enables the behaviour I am describing.

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to