| commit | f5b7ce1b9041d19658b79d8b956d7e79ec6006bd | |
| author | Jonathan Nieder <jrnieder@gmail.com> | |
| Sat, 21 May 2011 19:40:32 +0000 (21 14:40 -0500) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sun, 22 May 2011 05:29:33 +0000 (21 22:29 -0700) | ||
| tree | f2c08a7d7ea38f35c6138eb5a413d51f0a7c0329 | treesnapshot (tar.gz zip) |
| parent | ea2ca4497bdb716977a3e2526780635cb6bac513 | commitdiff |
tests: make test_expect_code quieter on success
A command exiting with the expected status is not particularly
notable.
While the indication of progress might be useful when tracking down
where in a test a failure has happened, the same applies to most other
test helpers, which are quiet about success, so this single helper's
output stands out in an unpleasant way. An alternative method for
showing progress information might to invent a --progress option that
runs tests with "set -x", or until that is available, to run tests
using commands like
prove -v -j2 --shuffle --exec='sh -x' t2202-add-addremove.sh
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
A command exiting with the expected status is not particularly
notable.
While the indication of progress might be useful when tracking down
where in a test a failure has happened, the same applies to most other
test helpers, which are quiet about success, so this single helper's
output stands out in an unpleasant way. An alternative method for
showing progress information might to invent a --progress option that
runs tests with "set -x", or until that is available, to run tests
using commands like
prove -v -j2 --shuffle --exec='sh -x' t2202-add-addremove.sh
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/test-lib.sh | diffblobblamehistory |