From: Junio C Hamano <gitster@pobox.com>
To: Siddharth Shrimali <r.siddharth.shrimali@gmail.com>
Cc: git@vger.kernel.org, abdobngad@gmail.com, ps@pks.im,
bence@ferdinandy.com, john.a.passaro@gmail.com
Subject: Re: [PATCH 1/3] t7004: drop hardcoded tag count in invalid name test
Date: Tue, 14 Apr 2026 09:54:23 -0700 [thread overview]
Message-ID: <xmqqmrz5bhz4.fsf@gitster.g> (raw)
In-Reply-To: <20260414141828.27576-2-r.siddharth.shrimali@gmail.com> (Siddharth Shrimali's message of "Tue, 14 Apr 2026 19:48:26 +0530")
Siddharth Shrimali <r.siddharth.shrimali@gmail.com> writes:
> The test 'trying to create a tag with a non-valid name should fail',
> checked that exactly one tag existed in the repository before and after
> attempting to create invalid tags.
>
> As pointed out by Junio, this makes the test brittle by relying on a
> specific global tag count. If future tests are added or removed before
> this test, the expected state changes and this test would break for
> completely unrelated reasons.
>
> Since we already use 'test_must_fail' to guarantee that the invalid
> tags are rejected by Git, counting the tags before and after is redundant.
>
> Drop the 'test_line_count = 1' checks so the test doesn't rely on the
> exact number of tags left behind by earlier tests.
The only thing I suggested was that relying on exact state before
this test makes this test brittle. I do not necessarily think
"redundant" is bad. Having belt-and-suspenders sometimes help.
Alternatively, if we wanted to catch a bug where "git tag" exits
with a non-zero status, satisfying test_must_fail, but still creates
the requested tag, then we could do
git tag -l >tags-before &&
test_must_fail git tag "" &&
... random attempts to create with invalid names ...
test_must_fail git tag "other~tag" &&
git tag -l >tags-after &&
test_cmp tags-before tags-after
instead. And that is a belt-and-suspenders approach.
Having said that, the patch is already an improvement, so let's take
it as is. Unless there are other things we may want to improve in
this or other patches in the series, that is.
Thanks.
> Suggested-by: Junio C Hamano <gitster@pobox.com>
> Signed-off-by: Siddharth Shrimali <r.siddharth.shrimali@gmail.com>
> ---
> t/t7004-tag.sh | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/t/t7004-tag.sh b/t/t7004-tag.sh
> index faf7d97fc4..6ca5c75b57 100755
> --- a/t/t7004-tag.sh
> +++ b/t/t7004-tag.sh
> @@ -191,15 +191,11 @@ test_expect_success 'trying to create a tag with the name of one existing should
> '
>
> test_expect_success 'trying to create a tag with a non-valid name should fail' '
> - git tag -l >actual &&
> - test_line_count = 1 actual &&
> test_must_fail git tag "" &&
> test_must_fail git tag .othertag &&
> test_must_fail git tag "other tag" &&
> test_must_fail git tag "othertag^" &&
> - test_must_fail git tag "other~tag" &&
> - git tag -l >actual &&
> - test_line_count = 1 actual
> + test_must_fail git tag "other~tag"
> '
>
> test_expect_success 'creating a tag using HEAD directly should succeed' '
next prev parent reply other threads:[~2026-04-14 16:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 14:18 [PATCH 0/3] t7004: cleanup and modernize brittle tests Siddharth Shrimali
2026-04-14 14:18 ` [PATCH 1/3] t7004: drop hardcoded tag count in invalid name test Siddharth Shrimali
2026-04-14 16:54 ` Junio C Hamano [this message]
2026-04-20 7:13 ` Patrick Steinhardt
2026-04-14 14:18 ` [PATCH 2/3] t7004: dynamically grab expected state in tests Siddharth Shrimali
2026-04-14 17:00 ` Junio C Hamano
2026-04-14 14:18 ` [PATCH 3/3] t7004: avoid subshells to capture git exit codes Siddharth Shrimali
2026-04-21 5:33 ` [PATCH v2 0/3] t7004: cleanup and modernize brittle tests Siddharth Shrimali
2026-04-21 5:33 ` [PATCH v2 1/3] t7004: drop hardcoded tag count for state verification Siddharth Shrimali
2026-04-21 5:33 ` [PATCH v2 2/3] t7004: dynamically grab expected state in tests Siddharth Shrimali
2026-04-21 5:33 ` [PATCH v2 3/3] t7004: avoid subshells to capture git exit codes Siddharth Shrimali
2026-04-21 5:38 ` [PATCH v2 0/3] t7004: cleanup and modernize brittle tests Patrick Steinhardt
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=xmqqmrz5bhz4.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=abdobngad@gmail.com \
--cc=bence@ferdinandy.com \
--cc=git@vger.kernel.org \
--cc=john.a.passaro@gmail.com \
--cc=ps@pks.im \
--cc=r.siddharth.shrimali@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