Re: [PATCH v3 2/7] t/t7510: check the validation of the new config gpg.format
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jul 16, 2018, 20:15 UTC
- Message-ID
- <xmqqd0vnszs4.fsf@gitster-ct.c.googlers.com>
- In-Reply-To
- <e3fc5449ef1fe1d107e11c77f2e66d8d47a451db.1531470729.git.henning.schild@siemens.com>
Henning Schild <henning.schild@siemens.com> writes:
Show 25 quoted lines
> Test setting gpg.format to both invalid and valid values. > > Signed-off-by: Henning Schild <henning.schild@siemens.com> > --- > 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..1b6a1dd90 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 && > + git commit -S --amend -m "success" && > + test_config gpg.format malformed && > + test_must_fail git commit -S --amend -m "fail" > +' > + > test_done
Since we'd be doing case-sensitive value for gpg.format, this would have to change in a later iteration, I guess.