Allow better control of the set of tests that will be executed for a
single test suite. Mostly useful while debugging or developing as it
allows to focus on a specific test.
Signed-off-by: Ilya Bobyr <ilya.bobyr@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
@ -104,6 +104,12 @@ appropriately before running "make".
@@ -104,6 +104,12 @@ appropriately before running "make".
This causes additional long-running tests to be run (where
available), for more exhaustive testing.
-r::
--run=<test-selector>::
Run only the subset of tests indicated by
<test-selector>. See section "Skipping Tests" below for
<test-selector> syntax.
--valgrind=<tool>::
Execute all Git binaries under valgrind tool <tool> and exit
with status 126 on errors (just like regular tests, this will
@ -191,10 +197,77 @@ and either can match the "t[0-9]{4}" part to skip the whole
@@ -191,10 +197,77 @@ and either can match the "t[0-9]{4}" part to skip the whole
test, or t[0-9]{4} followed by ".$number" to say which
particular test to skip.
Note that some tests in the existing test suite rely on previous
test item, so you cannot arbitrarily disable one and expect the
remainder of test to check what the test originally was intended
to check.
For an individual test suite --run could be used to specify that
only some tests should be run or that some tests should be
excluded from a run.
The argument for --run is a list of individual test numbers or
ranges with an optional negation prefix that define what tests in
a test suite to include in the run. A range is two numbers
separated with a dash and matches a range of tests with both ends
been included. You may omit the first or the second number to
mean "from the first test" or "up to the very last test"
respectively.
Optional prefix of '!' means that the test or a range of tests
should be excluded from the run.
If --run starts with an unprefixed number or range the initial
set of tests to run is empty. If the first item starts with '!'
all the tests are added to the initial set. After initial set is
determined every test number or range is added or excluded from
the set one by one, from left to right.
Individual numbers or ranges could be separated either by a space
or a comma.
For example, to run only tests up to a specific test (21), one
could do this:
$ sh ./t9200-git-cvsexport-commit.sh --run='1-21'
or this:
$ sh ./t9200-git-cvsexport-commit.sh --run='-21'
Common case is to run several setup tests (1, 2, 3) and then a
specific test (21) that relies on that setup:
$ sh ./t9200-git-cvsexport-commit.sh --run='1 2 3 21'
or:
$ sh ./t9200-git-cvsexport-commit.sh --run=1,2,3,21
or:
$ sh ./t9200-git-cvsexport-commit.sh --run='-3 21'
As noted above, the test set is built going though items left to
right, so this:
$ sh ./t9200-git-cvsexport-commit.sh --run='1-4 !3'
will run tests 1, 2, and 4. Items that comes later have higher
precendence. It means that this:
$ sh ./t9200-git-cvsexport-commit.sh --run='!3 1-4'
would just run tests from 1 to 4, including 3.
You may use negation with ranges. The following will run all
test in the test suite except from 7 up to 11:
$ sh ./t9200-git-cvsexport-commit.sh --run='!7-11'
Some tests in a test suite rely on the previous tests performing
certain actions, specifically some tests are designated as
"setup" test, so you cannot _arbitrarily_ disable one test and
expect the rest to function correctly.
--run is mostly useful when you want to focus on a specific test
and know what setup is needed for it. Or when you want to run