| commit | f445500e4dd79ad0c4f6cf1c4949f01f155142f7 | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Tue, 4 Jun 2013 16:50:12 +0000 (4 09:50 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 4 Jun 2013 20:36:54 +0000 (4 13:36 -0700) | ||
| tree | 792240be533e8032a274c0ae4b22e3a1173148b5 | treesnapshot (tar.gz zip) |
| parent | 4b8f772ce4df667583243e434ca0548d5b84b3a6 | commitdiff |
t/README: test_must_fail is for testing Git
When a test wants to make sure there is no <string> in an output
file, we should just say "! grep string output".
"test_must_fail" is there only to test Git command and catch unusual
deaths we know about (e.g. segv) as an error, not as an expected
failure. "test_must_fail grep string output" is unnecessary, as
we are not making sure the system binaries do not dump core or
anything like that.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
When a test wants to make sure there is no <string> in an output
file, we should just say "! grep string output".
"test_must_fail" is there only to test Git command and catch unusual
deaths we know about (e.g. segv) as an error, not as an expected
failure. "test_must_fail grep string output" is unnecessary, as
we are not making sure the system binaries do not dump core or
anything like that.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/README | diffblobblamehistory |