From: Sverre Rabbelier <srabbelier@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Git List" <git@vger.kernel.org>
Cc: Sverre Rabbelier <srabbelier@gmail.com>
Subject: [RFC PATCH 3/3] fast-import: test the new option command
Date: Sat, 1 Aug 2009 22:06:10 -0700 [thread overview]
Message-ID: <1249189570-26576-4-git-send-email-srabbelier@gmail.com> (raw)
In-Reply-To: <1249189570-26576-3-git-send-email-srabbelier@gmail.com>
Test the new 'option' command to fast-import to make sure that they
indeed affect the behavior in the same way as the commandline
options.
Signed-off-by: Sverre Rabbelier <srabbelier@gmail.com>
---
Since the option code is now very similar, I feel confident that
it works after testing two random [0] options.
[0] where with random I mean 'easy to test'
t/t9300-fast-import.sh | 33 +++++++++++++++++++++++++++++++++
1 files changed, 33 insertions(+), 0 deletions(-)
diff --git a/t/t9300-fast-import.sh b/t/t9300-fast-import.sh
index 821be7c..a5afe9a 100755
--- a/t/t9300-fast-import.sh
+++ b/t/t9300-fast-import.sh
@@ -1088,4 +1088,37 @@ INPUT_END
test_expect_success 'P: fail on blob mark in gitlink' '
test_must_fail git fast-import <input'
+###
+### series Q (options)
+###
+
+cat >input << EOF
+option quiet
+blob
+data 3
+hi
+
+EOF
+
+touch empty
+
+test_expect_success 'Q: quiet option results in no stats being output' '
+ cat input | git fast-import 2> output &&
+ test_cmp empty output
+'
+
+cat >input << EOF
+option export-marks git.marks
+blob
+mark :1
+data 3
+hi
+
+EOF
+
+test_expect_success \
+ 'Q: export-marks option results in a marks file being created' \
+ 'cat input | git fast-import 2> output &&
+ grep :1 git.marks'
+
test_done
--
1.6.4.15.g8b2be
next prev parent reply other threads:[~2009-08-02 5:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 1:29 option directive to fast-import Sverre Rabbelier
2009-08-02 5:06 ` [RFC PATCH 0/3] fast-import: add option command Sverre Rabbelier
2009-08-02 5:06 ` [RFC PATCH 1/2] fast-import: put option parsing code in seperate functions Sverre Rabbelier
2009-08-02 5:06 ` [RFC PATCH 2/2] fast-import: add option command Sverre Rabbelier
2009-08-02 5:06 ` Sverre Rabbelier [this message]
2009-08-02 7:09 ` [RFC PATCH v1a 1/3] fast-import: put option parsing code in seperate functions Sverre Rabbelier
2009-08-03 0:15 ` [RFC PATCH 0/3] fast-import: add option command Shawn O. Pearce
2009-08-03 4:31 ` Sverre Rabbelier
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=1249189570-26576-4-git-send-email-srabbelier@gmail.com \
--to=srabbelier@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/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).