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

Re: [PATCH 1/4] test-suite: adding a test for fast-export with tag variants

From
Erik Faye-Lund <kusmabite@googlemail.com>
Date
Mar 23, 2009, 00:55 UTC
Message-ID
<40aa078e0903221755n23457ba6m689aad34c0ec8214@mail.gmail.com>
In-Reply-To
<7vfxh59in9.fsf@gitster.siamese.dyndns.org>
On Mon, Mar 23, 2009 at 1:39 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 6 quoted lines
>> diff --git a/t/t9302-fast-export-tags.sh b/t/t9302-fast-export-tags.sh
>> new file mode 100644
>
> Make it executable if you need to add a new script, but shouldn't these
> small tests be done as an addition to existing t9301, not as a brand new
> script?
Sure, will do. I just have to figure out how to make it executable in windows ;)

As this is my first test, I was wondering a bit about how much I could depend on the state of the repo, so I was a bit reluctant to add it to the same test. But I guess it's easier for everyone in the long term to put it into the same test, so I'll give it a go.

Show 12 quoted lines
>> +test_expect_success 'tree_tag'        'git fast-export tree_tag'
>> +test_expect_success 'tree_tag-obj'    'git fast-export tree_tag-obj'
>> +test_expect_success 'tag-obj_tag'     'git fast-export tag-obj_tag'
>> +test_expect_success 'tag-obj_tag-obj' 'git fast-export tag-obj_tag-obj'
>> +
>> +test_done
>
> The purpose of the first patch that adds tests is to expose existing
> problems, and it is better to say test_expect_failure in them.  Later
> patch to fix these issues will contain code change and also change to flip
> some of the expect_failure to expect_success, and that way we can see what
> issue is fixed with which patch more easily.

Sure, will do. I was a bit lazy, but updating it as we go will make stuff easier in the future.

> These tests seem to only care about fast-export not dying, but don't we
> also want to check if they produce correct results?

Well, yeah. But I was working mainly on fixing a crash-bug here, and I don't think I know enough about the correct output of fast-export to pull this off. Perhaps tighting up the test is something someone else would care to do?

-- 
Erik "kusma" Faye-Lund
kusmabite@gmail.com
(+47) 986 59 656
Previous: Junio C HamanoNext: Junio C Hamano
Message 8 of 9 in “test-suite: adding a test for fast-export with tag variants”
  1. 1/4 test-suite: adding a test for fast-export with tag variantsErik Faye-Lund, Mar 22, 2009
  2. 2/4 builtin-fast-export.c: turn error into warningErik Faye-Lund, Mar 22, 2009
  3. 3/4 builtin-fast-export.c: fix crash on tagged treesErik Faye-Lund, Mar 22, 2009
  4. 4/4 builtin-fast-export.c: handle nested tagsErik Faye-Lund, Mar 22, 2009
  5. Junio C HamanoMar 23, 2009
  6. Erik Faye-LundMar 23, 2009
  7. Junio C HamanoMar 23, 2009
  8. Erik Faye-LundMar 23, 2009
  9. Junio C HamanoMar 23, 2009

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.