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

Re: [PATCH] Use test_expect_success for test setups

From
Brian Gernhardt <brian@gernhardtsoftware.com>
Date
Mar 20, 2010, 15:58 UTC
Message-ID
<2DDEFE95-02A7-4DAE-B233-ABE1545EDB65@gernhardtsoftware.com>
In-Reply-To
<7v7hp7ov8c.fsf@alter.siamese.dyndns.org>
On Mar 20, 2010, at 11:42 AM, Junio C Hamano wrote:
Show 10 quoted lines
> Brian Gernhardt <brian@gernhardtsoftware.com> writes:
> 
>> Several tests did not use test_expect_success for their setup
>> commands.  Putting these start commands into the testing framework
>> means both that errors during setup will be caught quickly and that
>> non-error text will be suppressed without -v.
> 
> Nice.  Should the one in 4103 be three separate tests?  They seem to be
> preparing the set of test input files and are not expected to fail (unless
> of course you are futzing with diff-tree, but for that we have t4013).
I don't think they need to be.  t4103 was the first one I did and I did it as three tests since it was three separate "blocks".  I had also tried moving the diff-trees closer to where their result is used until I saw how much they were reused.
~~ Brian
Previous: Junio C HamanoNext: Brian Gernhardt
Message 3 of 4 in “Use test_expect_success for test setups”
  1. Use test_expect_success for test setupsBrian Gernhardt, Mar 20, 2010
  2. Junio C HamanoMar 20, 2010
  3. Brian GernhardtMar 20, 2010
  4. Use test_expect_success for test setupsBrian Gernhardt, Mar 20, 2010

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.