From: Patrick Steinhardt <ps@pks.im>
To: Aryan Pathania <contact@aynp.dev>
Cc: git@vger.kernel.org
Subject: Re: [GSoC PATCH] t9400: prefer test_path_* helper functions
Date: Mon, 10 Mar 2025 07:50:20 +0100 [thread overview]
Message-ID: <Z86LrOEhH3CJOIey@pks.im> (raw)
In-Reply-To: <20250308090358.25429-1-contact@aynp.dev>
On Sat, Mar 08, 2025 at 06:03:58PM +0900, Aryan Pathania wrote:
> use `test_path_*` instead of `test -[efd]` to avoid false complaints and
Nit: We want to have full sentences in commit messages. Those sentences
should start with an upper-case letter and end with punctuation.
> output when running the script with `-v` or `-x`
Hm. I'm not exactly sure what "false complaints" you are talking about
here. The benefit of `test_path_*`()` over `test -[efd]` is that they
actually print information _why_ they have failed, which may help devs
to figure out what's happening. So it's kind of the opposite of what you
say in the commit message: we're now printing _more_ output, not less.
> Signed-off-by: Aryan Pathania <contact@aynp.dev>
> ---
> t/t9400-git-cvsserver-server.sh | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/t/t9400-git-cvsserver-server.sh b/t/t9400-git-cvsserver-server.sh
> index e499c7f955..6c7cb1964c 100755
> --- a/t/t9400-git-cvsserver-server.sh
> +++ b/t/t9400-git-cvsserver-server.sh
> @@ -254,7 +254,7 @@ test_expect_success 'gitcvs.enabled = false' \
> true
> fi &&
> grep "GITCVS emulation disabled" cvs.log &&
> - test ! -d cvswork2'
> + test_path_is_missing cvswork2'
This isn't quite equivalent: we've been checking that the path is not a
directory before, but now we verify that the path doesn't exist. It's a
sensible change in this context though as our new assertion is stronger
than the old one, but it might make sense to point out in the commit
message.
> @@ -285,7 +285,7 @@ test_expect_success 'gitcvs.dbname' '
> GIT_DIR="$SERVERDIR" git config gitcvs.dbname %Ggitcvs.%a.%m.sqlite &&
> GIT_CONFIG="$git_config" cvs -Q co -d cvswork2 main >cvs.log 2>&1 &&
> test_cmp cvswork cvswork2 &&
> - test -f "$SERVERDIR/gitcvs.ext.main.sqlite" &&
> + test_path_is_file_not_symlink "$SERVERDIR/gitcvs.ext.main.sqlite" &&
> cmp "$SERVERDIR/gitcvs.main.sqlite" "$SERVERDIR/gitcvs.ext.main.sqlite"
> '
>
We tend to use `test_path_is_file` rather than
`test_path_is_file_not_symlink`, but I don't mind it too much.
Patrick
next prev parent reply other threads:[~2025-03-10 6:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 9:03 [GSoC PATCH] t9400: prefer test_path_* helper functions Aryan Pathania
2025-03-10 6:50 ` Patrick Steinhardt [this message]
2025-03-12 17:34 ` Aryan Pathania
2025-03-12 18:13 ` Junio C Hamano
2025-03-14 12:00 ` Aryan Pathania
2025-03-14 17:07 ` Junio C Hamano
2025-03-18 13:10 ` [GSoC PATCH v2] Use `test_path_*` helper functions instead of `test -[efd]` Aryan Pathania
2025-03-18 22:06 ` Eric Sunshine
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=Z86LrOEhH3CJOIey@pks.im \
--to=ps@pks.im \
--cc=contact@aynp.dev \
--cc=git@vger.kernel.org \
/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).