From: Junio C Hamano <gitster@pobox.com>
To: Erik Faye-Lund <kusmabite@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/4] test-suite: adding a test for fast-export with tag variants
Date: Sun, 22 Mar 2009 17:39:54 -0700 [thread overview]
Message-ID: <7vfxh59in9.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 1237758620-6116-1-git-send-email-kusmabite@gmail.com
Erik Faye-Lund <kusmabite@gmail.com> writes:
> Signed-off-by: Erik Faye-Lund <kusmabite@gmail.com>
> ---
> t/t9302-fast-export-tags.sh | 25 +++++++++++++++++++++++++
> 1 files changed, 25 insertions(+), 0 deletions(-)
> create mode 100644 t/t9302-fast-export-tags.sh
>
> 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?
> index 0000000..2ecac32
> --- /dev/null
> +++ b/t/t9302-fast-export-tags.sh
> @@ -0,0 +1,25 @@
> +#!/bin/sh
> +#
> +# Copyright (c) 2009 Erik Faye-Lund
> +#
> +
> +test_description='git fast-export tag variants'
> +. ./test-lib.sh
> +
> +test_expect_success 'setup' '
> + touch dummy &&
> + git add dummy &&
> + git commit -m "initial commit" &&
> + HEAD_TREE=`git show -s --pretty=raw HEAD | grep tree | sed "s/tree //"` &&
> + git tag tree_tag -m "tagging a tree" $HEAD_TREE &&
> + git tag -a tree_tag-obj -m "tagging a tree" $HEAD_TREE &&
> + git tag tag-obj_tag -m "tagging a tag" tree_tag-obj &&
> + git tag -a tag-obj_tag-obj -m "tagging a tag" tree_tag-obj
> +'
> +
> +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.
These tests seem to only care about fast-export not dying, but don't we
also want to check if they produce correct results?
next prev parent reply other threads:[~2009-03-23 0:41 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 ` Junio C Hamano [this message]
2009-03-23 0:55 ` [PATCH 1/4] test-suite: adding a test for fast-export with tag variants Erik Faye-Lund
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=7vfxh59in9.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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).