Thread (13 messages) flat view 13 messages, 2 authors, 2018-07-20

Re: [PATCH v4 2/7] t/t7510: check the validation of the new config gpg.format

From: Junio C Hamano <hidden>
Date: 2018-07-17 21:32:01

Henning Schild [off-list ref] writes:
quoted hunk ↗ jump to hunk
Test setting gpg.format to both invalid and valid values.

Signed-off-by: Henning Schild <redacted>
---
 t/t7510-signed-commit.sh | 9 +++++++++
 1 file changed, 9 insertions(+)
diff --git a/t/t7510-signed-commit.sh b/t/t7510-signed-commit.sh
index 6e2015ed9..7bdad570c 100755
--- a/t/t7510-signed-commit.sh
+++ b/t/t7510-signed-commit.sh
@@ -227,4 +227,13 @@ test_expect_success GPG 'log.showsignature behaves like --show-signature' '
 	grep "gpg: Good signature" actual
 '
 
+test_expect_success GPG 'check config gpg.format values' '
+	test_config gpg.format openpgp &&
+	git commit -S --amend -m "success" &&
+	test_config gpg.format OpEnPgP &&
+	test_must_fail git commit -S --amend -m "fail" &&
This second one is a good demonstration that the value for this
variable is case sensitive.
+	test_config gpg.format malformed &&
+	test_must_fail git commit -S --amend -m "fail"
And there is no longer a good reason to try another one.  Let's drop
this last/third case.
+'
+
 test_done
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help