From: Erik Faye-Lund <kusmabite@googlemail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Erik Faye-Lund <kusmabite@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/4] test-suite: adding a test for fast-export with tag variants
Date: Mon, 23 Mar 2009 01:55:15 +0100 [thread overview]
Message-ID: <40aa078e0903221755n23457ba6m689aad34c0ec8214@mail.gmail.com> (raw)
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:
>> 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.
>> +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
next prev parent reply other threads:[~2009-03-23 1:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 21:50 [PATCH 1/4] test-suite: adding a test for fast-export with tag variants Erik Faye-Lund
2009-03-22 21:50 ` [PATCH 2/4] builtin-fast-export.c: turn error into warning Erik Faye-Lund
2009-03-22 21:50 ` [PATCH 3/4] builtin-fast-export.c: fix crash on tagged trees Erik Faye-Lund
2009-03-22 21:50 ` [PATCH 4/4] builtin-fast-export.c: handle nested tags Erik Faye-Lund
2009-03-23 0:39 ` [PATCH 3/4] builtin-fast-export.c: fix crash on tagged trees Junio C Hamano
2009-03-23 1:01 ` Erik Faye-Lund
2009-03-23 0:39 ` [PATCH 1/4] test-suite: adding a test for fast-export with tag variants Junio C Hamano
2009-03-23 0:55 ` Erik Faye-Lund [this message]
2009-03-23 3:41 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2009-03-23 12:53 Erik Faye-Lund
2009-03-29 20:05 ` Erik Faye-Lund
2009-03-29 21:32 ` Junio C Hamano
2009-03-29 21:44 ` Erik Faye-Lund
2009-03-30 2:50 ` Junio C Hamano
2009-03-30 9:08 Erik Faye-Lund
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40aa078e0903221755n23457ba6m689aad34c0ec8214@mail.gmail.com \
--to=kusmabite@googlemail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kusmabite@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).