From: Adam Spiers <git@adamspiers.org>
To: git list <git@vger.kernel.org>
Cc: Zoltan Klinger <zoltan.klinger@gmail.com>
Subject: [PATCH 1/2] t0008: document test_expect_success_multi
Date: Tue, 19 Feb 2013 14:06:22 +0000 [thread overview]
Message-ID: <1361282783-1413-1-git-send-email-git@adamspiers.org> (raw)
In-Reply-To: <CAOkDyE_96Ef5CjoxNk3mbsNi+ZAuv6XeHcO7r8RQ-Of5ELsuKw@mail.gmail.com>
test_expect_success_multi() helper function warrants some explanation,
since at first sight it may seem like generic test framework plumbing,
but is in fact specific to testing check-ignore, and allows more
thorough testing of the various output formats without significantly
increase the size of t0008.
Signed-off-by: Adam Spiers <git@adamspiers.org>
---
t/t0008-ignores.sh | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/t/t0008-ignores.sh b/t/t0008-ignores.sh
index d7df719..ebe7c70 100755
--- a/t/t0008-ignores.sh
+++ b/t/t0008-ignores.sh
@@ -75,6 +75,16 @@ test_check_ignore () {
stderr_empty_on_success "$expect_code"
}
+# Runs the same code with 3 different levels of output verbosity,
+# expecting success each time. Takes advantage of the fact that
+# check-ignore --verbose output is the same as normal output except
+# for the extra first column.
+#
+# Arguments:
+# - (optional) prereqs for this test, e.g. 'SYMLINKS'
+# - test name
+# - output to expect from -v / --verbose mode
+# - code to run (should invoke test_check_ignore)
test_expect_success_multi () {
prereq=
if test $# -eq 4
--
1.8.1.291.g0730ed6
next prev parent reply other threads:[~2013-02-19 14:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 5:24 [BUG] git-check-ignore: Segmentation fault Zoltan Klinger
2013-02-19 13:40 ` Adam Spiers
2013-02-19 14:06 ` Adam Spiers [this message]
2013-02-19 14:06 ` [PATCH 2/2] check-ignore.c: fix segfault with '.' argument from repo root Adam Spiers
2013-02-19 17:54 ` Junio C Hamano
2013-02-19 19:07 ` Adam Spiers
2013-02-19 19:21 ` [PATCH v2 2/2] check-ignore.c, dir.c: " Adam Spiers
2013-02-19 19:59 ` Junio C Hamano
2013-02-19 22:03 ` Junio C Hamano
2013-02-20 1:57 ` Adam Spiers
2013-02-20 2:47 ` Junio C Hamano
2013-02-20 12:43 ` Adam Spiers
2013-02-20 1:30 ` Adam Spiers
2013-02-19 19:56 ` Re* [PATCH 2/2] check-ignore.c: " Junio C Hamano
2013-02-20 2:00 ` Adam Spiers
2013-02-20 2:53 ` Junio C Hamano
2013-02-20 10:47 ` Adam Spiers
2013-02-21 20:15 ` Junio C Hamano
2013-02-21 20:17 ` [PATCH 1/2] format-patch: rename "no_inline" field Junio C Hamano
2013-02-21 20:26 ` [PATCH 2/2] format-patch: --inline-single Junio C Hamano
2013-02-21 23:13 ` Jeff King
2013-02-21 23:41 ` Junio C Hamano
2013-02-21 23:47 ` Junio C Hamano
2013-02-22 15:32 ` Adam Spiers
2013-02-22 16:47 ` Junio C Hamano
2013-02-22 17:23 ` Jeff King
2013-02-19 17:37 ` [PATCH 1/2] t0008: document test_expect_success_multi Junio C Hamano
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=1361282783-1413-1-git-send-email-git@adamspiers.org \
--to=git@adamspiers.org \
--cc=git@vger.kernel.org \
--cc=zoltan.klinger@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).