From: santiago@nyu.edu
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Eric Sunshine <sunshine@sunshineco.com>,
Santiago Torres <santiago@nyu.edu>
Subject: [PATCH v3 2/4] t/t7030-verify-tag.sh: Adds validation for multiple tags
Date: Sat, 2 Apr 2016 19:16:13 -0400 [thread overview]
Message-ID: <1459638975-17705-3-git-send-email-santiago@nyu.edu> (raw)
In-Reply-To: <1459638975-17705-1-git-send-email-santiago@nyu.edu>
From: Santiago Torres <santiago@nyu.edu>
The verify-tag command supports mutliple tag names as an argument.
However, no previous tests try to verify multiple tags at once. This
test runs the verify-tag command against three trusted tags (created
previously), and ensures that:
1) Three tags are verified appropriately (grep GOODSIG) and
2) The three tags verified are indeed differently (uniq
-u)
Signed-off-by: Santiago Torres <santiago@nyu.edu>
---
t/t7030-verify-tag.sh | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/t/t7030-verify-tag.sh b/t/t7030-verify-tag.sh
index 4608e71..5918f86 100755
--- a/t/t7030-verify-tag.sh
+++ b/t/t7030-verify-tag.sh
@@ -112,4 +112,12 @@ test_expect_success GPG 'verify signatures with --raw' '
)
'
+test_expect_success GPG 'verify multiple tags' '
+ git verify-tag -v --raw fourth-signed sixth-signed seventh-signed 2>actual 1> tagnames &&
+ grep -c "GOODSIG" actual > count &&
+ ! grep "BADSIG" actual &&
+ grep -E "tag\ .*" tagnames | uniq -u | wc - l | grep "3"
+'
+
+
test_done
--
2.8.0
next prev parent reply other threads:[~2016-04-02 23:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 23:16 [PATCH v3 0/4] tag: move PGP verification code to tag.c santiago
2016-04-02 23:16 ` [PATCH v3 1/4] builtin/verify-tag.c: Ignore SIGPIPE on gpg-interface santiago
2016-04-03 4:30 ` Jeff King
2016-04-03 6:50 ` Johannes Sixt
2016-04-03 21:46 ` Santiago Torres
2016-04-02 23:16 ` santiago [this message]
2016-04-03 4:40 ` [PATCH v3 2/4] t/t7030-verify-tag.sh: Adds validation for multiple tags Jeff King
2016-04-03 7:59 ` Eric Sunshine
2016-04-03 13:07 ` Jeff King
2016-04-03 21:58 ` Santiago Torres
2016-04-04 1:38 ` Eric Sunshine
2016-04-04 13:41 ` Jeff King
2016-04-02 23:16 ` [PATCH v3 3/4] builtin/verify-tag: move verification code to tag.c santiago
2016-04-03 4:45 ` Jeff King
2016-04-03 8:11 ` Eric Sunshine
2016-04-03 8:19 ` Eric Sunshine
2016-04-03 21:53 ` Santiago Torres
2016-04-02 23:16 ` [PATCH v3 4/4] tag: use pgp_verify_function in tag -v call santiago
2016-04-03 4:56 ` Jeff King
2016-04-03 21:43 ` Santiago Torres
2016-04-04 4:12 ` Santiago Torres
2016-04-04 13:38 ` Jeff King
2016-04-04 18:24 ` Santiago Torres
2016-04-04 20:19 ` Jeff King
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=1459638975-17705-3-git-send-email-santiago@nyu.edu \
--to=santiago@nyu.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=sunshine@sunshineco.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).