git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] t/README: unify documentation of test function args

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 25, 2011, 19:31 UTC
Message-ID
<7vzknei0vn.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4DB5BDBE.308@debugon.org>
Mathias Lafeldt <misfire@debugon.org> writes:
> Ah, okay. Is this true for test_expect_code too? It also has a git command
> in the example, but it says <command>, not <git-command>:
>
>  - test_expect_code <exit-code> <command>

I think that one is Ok as there is no git specific hacks in the semantics. It is a straight "Run this command, and make sure you get this exit code".

The "must-fail" is really a special case in that we just do not expect any failure, but expect a controlled failure. Currently we only catch segv, but we should anticipate that we will reject other types of uncontrolled failures in the future, and keeping the function "git-only" makes it easier to manage.

Previous: Mathias LafeldtNext: Mathias Lafeldt
Message 4 of 7 in “t/README: unify documentation of test function args”
  1. t/README: unify documentation of test function argsMathias Lafeldt, Apr 24, 2011
  2. Junio C HamanoApr 25, 2011
  3. Mathias LafeldtApr 25, 2011
  4. Junio C HamanoApr 25, 2011
  5. t/README: unify documentation of test function argsMathias Lafeldt, Apr 26, 2011
  6. Drew NorthupApr 26, 2011
  7. Junio C HamanoApr 27, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.