summaryrefslogtreecommitdiff
path: root/Documentation/git-merge-base.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2008-02-28 21:09:30 (GMT)
committerJunio C Hamano <gitster@pobox.com>2008-03-03 07:15:06 (GMT)
commit90d0ed96b76ee51f8ae6f32923b92e7b20ba73c0 (patch)
tree52960079fe7077394215af7fb5b2cac40c061c65 /Documentation/git-merge-base.txt
parentfcbcfe707ae23b37d72025a229f31c450fb4d3b3 (diff)
downloadgit-90d0ed96b76ee51f8ae6f32923b92e7b20ba73c0.zip
git-90d0ed96b76ee51f8ae6f32923b92e7b20ba73c0.tar.gz
git-90d0ed96b76ee51f8ae6f32923b92e7b20ba73c0.tar.bz2
tests: introduce test_must_fail
When we expect a git command to notice and signal errors, we carelessly wrote in our tests: test_expect_success 'reject bogus request' ' do something && do something else && ! git command ' but a non-zero exit could come from the "git command" segfaulting. A new helper function "tset_must_fail" is introduced and it is meant to be used to make sure the command gracefully fails (iow, dying and exiting with non zero status is counted as a failure to "gracefully fail"). The above example should be written as: test_expect_success 'reject bogus request' ' do something && do something else && test_must_fail git command ' Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-merge-base.txt')
0 files changed, 0 insertions, 0 deletions