Jeff King [off-list ref] writes:
You can also note that if we ever delete a test script, it will still be
mentioned in prove's state file. I think prove is smart enough to
realize it went away and not bother you.
The inverse might be more problematic. When we add a new test
script (which we still do from time to time), does prove notice
that we asked it to run more tests than it already knows about?
On Tue, Jan 19, 2016 at 03:26:04PM -0800, Junio C Hamano wrote:
Jeff King [off-list ref] writes:
quoted
You can also note that if we ever delete a test script, it will still be
mentioned in prove's state file. I think prove is smart enough to
realize it went away and not bother you.
The inverse might be more problematic. When we add a new test
script (which we still do from time to time), does prove notice
that we asked it to run more tests than it already knows about?
Yes. It runs the union of the state-file and what you give it on the
command line. E.g.:
$ rm .prove
$ prove --state=slow,save t0000-basic.sh
No saved state, selection will be empty
t0000-basic.sh .. ok
All tests successful.
Files=1, Tests=77, 1 wallclock secs ( 0.03 usr 0.00 sys + 0.08 cusr 0.06 csys = 0.17 CPU)
Result: PASS
$ prove --state=slow,save t0001-init.sh
t0000-basic.sh .. ok
t0001-init.sh ... ok
All tests successful.
Files=2, Tests=113, 1 wallclock secs ( 0.03 usr 0.00 sys + 0.06 cusr 0.10 csys = 0.19 CPU)
Result: PASS
-Peff