From: Jeff King <peff@peff.net>
To: Conrad Irwin <conrad.irwin@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Test atomic git-commit --interactive
Date: Tue, 10 May 2011 15:43:34 -0400 [thread overview]
Message-ID: <20110510194334.GA14456@sigill.intra.peff.net> (raw)
In-Reply-To: <1305054751-12327-1-git-send-email-conrad.irwin@gmail.com>
On Tue, May 10, 2011 at 12:12:31PM -0700, Conrad Irwin wrote:
> +test_expect_success PERL \
> + "--interactive doesn't change index if editor aborts" \
> + "EDITOR=false echo zoo >file && \
This EDITOR bit does nothing, since it sets the value only for the
"echo" command. The test happens to do what you want, though, since we
set EDITOR to ":" in test-lib.sh, and that is also a fine value for your
test (it's probably a better test, anyway; it simulates the user
aborting with an empty message instead of the editor crashing).
Even though the implicit EDITOR works, I think it makes sense to be
explicit that it is something we are relying on. So we need to put it in
front of the "git commit" invocation, like:
EDITOR=: test_must_fail git commit --interactive
Unfortunately, some shells do behave reasonably when setting single-shot
environment variables with functions, so we are stuck with:
(EDITOR=: && export EDITOR &&
test_must_fail git commit --interactive)
> + test_must_fail git diff --exit-code > diff1 && \
You can drop the backslash-continuation on lines that end with "&&" or
"|", which makes things a bit more readable.
You do still need ones for:
test_expect_success "description" \
"actual test"
The usual style for our tests is:
test_expect_success 'description' '
actual test
'
but this particular script does not follow that, so it's probably more
sensible to follow the surrounding style as you did.
> + (echo u ; echo '*' ; echo q) |\
> + test_must_fail git commit --interactive && \
> + git diff > diff2 && \
Minor style nit: we usually write ">file" without the space.
> + git diff --no-index diff1 diff2"
When comparing results with a simple diff, we generally use "test_cmp",
so that unrelated tests do not rely on "git diff --no-index".
So the result should look like:
diff --git a/t/t7501-commit.sh b/t/t7501-commit.sh
index 7f7f7c7..ccb0b95 100755
--- a/t/t7501-commit.sh
+++ b/t/t7501-commit.sh
@@ -131,6 +131,16 @@ test_expect_success PERL \
"interactive add" \
"echo 7 | git commit --interactive | grep 'What now'"
+test_expect_success PERL \
+ "--interactive doesn't change index if editor aborts" \
+ "echo zoo >file &&
+ test_must_fail git diff --exit-code >diff1 &&
+ (echo u ; echo '*' ; echo q) |
+ (EDITOR=: && export EDITOR &&
+ test_must_fail git commit --interactive) &&
+ git diff >diff2 &&
+ test_cmp diff1 diff2"
+
test_expect_success \
"showing committed revisions" \
"git rev-list HEAD >current"
-Peff
next prev parent reply other threads:[~2011-05-10 19:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 5:59 [PATCH v3 0/3] Git commit --patch (again) conrad.irwin
2011-05-07 5:59 ` [PATCH v3 1/3] Use a temporary index for git commit --interactive conrad.irwin
2011-05-07 6:00 ` [PATCH v3 2/3] Allow git commit --interactive with paths conrad.irwin
2011-05-07 6:00 ` [PATCH v3 3/3] Add support for -p/--patch to git-commit conrad.irwin
2011-05-07 10:46 ` Valentin Haenel
2011-05-07 17:55 ` Conrad Irwin
2011-05-07 17:58 ` [PATCH v4 " Conrad Irwin
2011-05-08 19:27 ` Junio C Hamano
2011-05-07 17:59 ` [PATCH] Add commit to list of config.singlekey commands Conrad Irwin
2011-05-07 9:49 ` [PATCH v3 0/3] Git commit --patch (again) Sverre Rabbelier
2011-05-09 14:44 ` Jeff King
2011-05-09 16:53 ` Junio C Hamano
2011-05-09 22:08 ` Jeff King
2011-05-09 23:53 ` Junio C Hamano
2011-05-09 23:56 ` Junio C Hamano
2011-05-10 20:01 ` Jeff King
2011-05-10 19:56 ` Jeff King
2011-05-10 6:42 ` Conrad Irwin
2011-05-10 19:12 ` [PATCH] Test atomic git-commit --interactive Conrad Irwin
2011-05-10 19:43 ` Jeff King [this message]
2011-05-10 21:01 ` Conrad Irwin
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=20110510194334.GA14456@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=conrad.irwin@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).