From: Patrick Steinhardt <ps@pks.im>
To: Mahendra Dani <danimahendra0904@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/1] t1403: prefer test_path_exists helper function
Date: Mon, 3 Mar 2025 11:26:32 +0100 [thread overview]
Message-ID: <Z8WD2MeHpOH7Ni8A@pks.im> (raw)
In-Reply-To: <20250301105838.1481-2-danimahendra0904@gmail.com>
On Sat, Mar 01, 2025 at 04:28:38PM +0530, Mahendra Dani wrote:
> test -e does not provide a nice error message when
> we hit test failures, so use test_path_exists instead.
>
> Signed-off-by: Mahendra Dani <danimahendra0904@gmail.com>
> ---
> t/t1403-show-ref.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/t/t1403-show-ref.sh b/t/t1403-show-ref.sh
> index 9d698b3cc3..12f7b60024 100755
> --- a/t/t1403-show-ref.sh
> +++ b/t/t1403-show-ref.sh
> @@ -196,7 +196,7 @@ test_expect_success 'show-ref --verify with dangling ref' '
>
> remove_object() {
> file=$(sha1_file "$*") &&
> - test -e "$file" &&
> + test_path_exists "$file" &&
> rm -f "$file"
> } &&
The refactoring is true to the original spirit of the preimage indeed.
But we could also improve it even further if we verified that the path
not only exists, but exists and is a file via `test_path_is_file()`. If
we decide to do that we should also explain the change in the commit
message.
Thanks!
Patrick
next prev parent reply other threads:[~2025-03-03 10:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 10:58 [GSOC][PATCH 0/1] t1403: prefer test_path_exists helper function Mahendra Dani
2025-03-01 10:58 ` [PATCH 1/1] " Mahendra Dani
2025-03-03 10:26 ` Patrick Steinhardt [this message]
2025-03-04 2:27 ` Mahendra Dani
2025-03-04 12:05 ` Junio C Hamano
2025-03-04 17:24 ` Mahendra Dani
2025-03-04 17:26 ` Junio C Hamano
2025-03-04 17:35 ` Mahendra Dani
2025-03-04 17:44 ` Junio C Hamano
2025-03-04 17:49 ` Mahendra Dani
2025-03-04 18:07 ` Junio C Hamano
2025-03-04 17:35 ` Eric Sunshine
2025-03-04 17:49 ` Junio C Hamano
2025-03-04 18:07 ` Eric Sunshine
2025-03-04 18:28 ` Eric Sunshine
2025-03-04 18:30 ` Junio C Hamano
2025-03-04 9:15 ` [GSOC][PATCH v2 0/1] t1403: verify path exists and is a file Mahendra Dani
2025-03-04 9:41 ` [GSOC][PATCH v3 " Mahendra Dani
2025-03-04 9:41 ` [PATCH v3 1/1] t1403: verify that " Mahendra Dani
2025-03-04 18:05 ` Junio C Hamano
2025-03-04 18:06 ` Junio C Hamano
2025-03-04 18:13 ` Mahendra Dani
2025-03-04 11:23 ` [PATCH v4 0/1] t1403: verify " Mahendra Dani
2025-03-04 11:27 ` Mahendra Dani
2025-03-04 11:27 ` [PATCH v4 1/1] t1403: verify that " Mahendra Dani
2025-03-04 18:13 ` Junio C Hamano
2025-03-04 18:19 ` Mahendra Dani
2025-03-04 16:00 ` [GSOC][PATCH v3 0/1] t1403: verify " Junio C Hamano
2025-03-04 9:27 ` [PATCH v2 1/1] t1403: verify that " Mahendra Dani
2025-03-04 11:02 ` Patrick Steinhardt
2025-03-04 11:15 ` Mahendra Dani
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=Z8WD2MeHpOH7Ni8A@pks.im \
--to=ps@pks.im \
--cc=danimahendra0904@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).