diff options
author | Junio C Hamano <gitster@pobox.com> | 2013-07-05 01:15:48 -0700 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2013-07-05 01:15:48 -0700 |
commit | 04f2ddda8426d3ae46d52d9dcbfc00bd3c52e645 (patch) | |
tree | e5874fad2dc1692fe95b3e872f07f3e6d2b5761f /t/README | |
parent | Merge branch 'maint' (diff) | |
parent | perf-lib: fix start/stop of perf tests (diff) | |
download | tgif-04f2ddda8426d3ae46d52d9dcbfc00bd3c52e645.tar.xz |
Merge branch 'tr/test-v-and-v-subtest-only'
Allows N instances of tests run in parallel, each running 1/N parts
of the test suite under Valgrind, to speed things up.
* tr/test-v-and-v-subtest-only:
perf-lib: fix start/stop of perf tests
test-lib: support running tests under valgrind in parallel
test-lib: allow prefixing a custom string before "ok N" etc.
test-lib: valgrind for only tests matching a pattern
test-lib: verbose mode for only tests matching a pattern
test-lib: self-test that --verbose works
test-lib: rearrange start/end of test_expect_* and test_skip
test-lib: refactor $GIT_SKIP_TESTS matching
test-lib: enable MALLOC_* for the actual tests
Diffstat (limited to 't/README')
-rw-r--r-- | t/README | 10 |
1 files changed, 10 insertions, 0 deletions
@@ -76,6 +76,11 @@ appropriately before running "make". command being run and their output if any are also output. +--verbose-only=<pattern>:: + Like --verbose, but the effect is limited to tests with + numbers matching <pattern>. The number matched against is + simply the running count of the test within the file. + --debug:: This may help the person who is developing a new test. It causes the command defined with test_debug to run. @@ -121,6 +126,11 @@ appropriately before running "make". the 't/valgrind/' directory and use the commands under 't/valgrind/bin/'. +--valgrind-only=<pattern>:: + Like --valgrind, but the effect is limited to tests with + numbers matching <pattern>. The number matched against is + simply the running count of the test within the file. + --tee:: In addition to printing the test output to the terminal, write it to files named 't/test-results/$TEST_NAME.out'. |