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

How to re-use setups in multiple tests?

From
TCTom Clarke <tom@u2i.com>
Date
Oct 1, 2007, 10:27 UTC
Message-ID
<550f9510710010327l3e729ff1tbbb9b6c674c1cb11@mail.gmail.com>

I'm wondering if there's a pattern for re-using setups across several tests, similar to how a setUp function is used in xUnit. The problem is I need the setup to actually be re-run, for each test to start from a clean slate, so using the following doesn't work as the setup is just run before the first test.

test_expect_success setup '
     # setup repostory to a particular state
'
test_expect_success test1 '
    # some test that expects the state to be as defined in setup, and
changes state of repository
'
test_expect_success test2 '
    # another test that expects the state to be as defined in setup
'

Is there a convention for doing this that's already used? Perhaps pulling the setup code into a function or duplicating the code? Or is it better to create a separate test file for tests that need to be isolated?

Thanks,
-Tom
Next: Johannes Schindelin
Message 1 of 6 in “How to re-use setups in multiple tests?”
  1. Tom ClarkeOct 1, 2007
  2. Johannes SchindelinOct 1, 2007
  3. Tom ClarkeOct 1, 2007
  4. Johannes SchindelinOct 1, 2007
  5. Tom ClarkeOct 1, 2007
  6. Karl HasselströmOct 1, 2007

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.