From: Patrick Steinhardt <ps@pks.im>
To: matteobagnolini <matteobagnolini2003@gmail.com>
Cc: git@vger.kernel.org, John Cai <johncai86@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] t7110: Replace `test -f` and `! test -f` with `test_path_is_file` and `test_path_is_missing` for improved debuggability when failing.
Date: Fri, 3 Jan 2025 12:41:24 +0100 [thread overview]
Message-ID: <Z3fM1bT2Z_0GoD4w@pks.im> (raw)
In-Reply-To: <20250101225915.65185-1-matteobagnolini2003@gmail.com>
On Wed, Jan 01, 2025 at 11:59:14PM +0100, matteobagnolini wrote:
The commit subject is overly long. We typically try to restrict them to
at most 72 characters. Furthermore, the part after the subsystem should
start with a lower-case letter. Suggestion:
t7110: replace `test -f` with `test_path_is_*` helpers
> `test -f` and `! test -f` do not provide clear error messages when they fail.
> To enanche debuggability, use `test_path_is_file` and `test_path_is_missing`,
s/enanche/enhance
> which instead provides more informative error messages.
s/provides/provide
It looks like you intended to start a new paragraph here. These should
typically be separated by an empty line.
> Note that `! test -f` checks if a path is not a file, while
> `test_path_is_missing` verifies that a path does not exist. In this specific
> case the tests are meant to check the absence of the path, making
> `test_path_is_missing` a valid replacement.
Makes sense.
> Signed-off-by: matteobagnolini <matteobagnolini2003@gmail.com>
We typically prefer proper legal names in the SOB.
> diff --git a/t/t7110-reset-merge.sh b/t/t7110-reset-merge.sh
> index 61669a2d21..9a335071af 100755
> --- a/t/t7110-reset-merge.sh
> +++ b/t/t7110-reset-merge.sh
> @@ -270,13 +270,13 @@ test_expect_success '--merge is ok with added/deleted merge' '
> git reset --hard third &&
> rm -f file2 &&
> test_must_fail git merge branch3 &&
> - ! test -f file2 &&
> - test -f file3 &&
> + test_path_is_missing file2 &&
> + test_path_is_file file3 &&
> git diff --exit-code file3 &&
> git diff --exit-code branch3 file3 &&
> git reset --merge HEAD &&
> - ! test -f file3 &&
> - ! test -f file2 &&
> + test_path_is_missing file3 &&
> + test_path_is_missing file2 &&
> git diff --exit-code --cached
> '
>
> @@ -284,8 +284,8 @@ test_expect_success '--keep fails with added/deleted merge' '
> git reset --hard third &&
> rm -f file2 &&
> test_must_fail git merge branch3 &&
> - ! test -f file2 &&
> - test -f file3 &&
> + test_path_is_missing file2 &&
> + test_path_is_file file3 &&
> git diff --exit-code file3 &&
> git diff --exit-code branch3 file3 &&
> test_must_fail git reset --keep HEAD 2>err.log &&
The changes themselves look obviously good to me, thanks!
Patrick
next prev parent reply other threads:[~2025-01-03 11:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 22:59 [PATCH] t7110: Replace `test -f` and `! test -f` with `test_path_is_file` and `test_path_is_missing` for improved debuggability when failing matteobagnolini
2025-01-03 11:41 ` Patrick Steinhardt [this message]
2025-01-03 13:00 ` [PATCH v2] t7110: replace `test -f` with `test_path_is_*` helpers Matteo Bagnolini
2025-01-03 13:12 ` Patrick Steinhardt
2025-01-03 16:25 ` Junio C Hamano
2025-01-03 17:27 ` Matteo Bagnolini
2025-01-03 18:06 ` Junio C Hamano
2025-01-03 19:07 ` Matteo Bagnolini
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=Z3fM1bT2Z_0GoD4w@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johncai86@gmail.com \
--cc=matteobagnolini2003@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.