summaryrefslogtreecommitdiff
path: root/Documentation
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-02-29 08:00:29 (GMT)
commit7435982102093179474a128648179a44042d8a1c (patch)
tree0241bd25b24d222758ed70363340379fec5d12e8 /Documentation
parent301e42edc3fa277059be97b3be5b97d86ddc9d9f (diff)
downloadgit-7435982102093179474a128648179a44042d8a1c.zip
git-7435982102093179474a128648179a44042d8a1c.tar.gz
git-7435982102093179474a128648179a44042d8a1c.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')
0 files changed, 0 insertions, 0 deletions