From: Ogundipe Sola Taiwo <ogundipesolataiwo12@gmail.com>
To: git@vger.kernel.org
Cc: Ogundipe Sola Taiwo <ogundipesolataiwo12@gmail.com>,
Christian Couder <christian.couder@gmail.com>,
Siddharth Asthana <siddharthasthana31@gmail.com>,
Usman Akinyemi <usmanakinyemi202@gmail.com>
Subject: [PATCH v2] t5300: modernize test path checks in t5300
Date: Tue, 27 Oct 2026 14:36:20 -0400 [thread overview]
Message-ID: <20261027183623.3600-1-ogundipesolataiwo12@gmail.com> (raw)
In-Reply-To: <20261023154851.7876-1-ogundipesolataiwo12@gmail.com>
Improves test t5300-pack-object by converting old-style
path checks to use the `test_path_is_file` helper function.
Signed-off-by: Ogundipe Sola Taiwo <ogundipesolataiwo12@gmail.com>
---
Changes in v2:
- Rephrase patch summary to remove redundant wording
t/t5300-pack-object.sh | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/t/t5300-pack-object.sh b/t/t5300-pack-object.sh
index aac139e6a0..e5ce478484 100755
--- a/t/t5300-pack-object.sh
+++ b/t/t5300-pack-object.sh
@@ -283,11 +283,11 @@ test_expect_success 'survive missing objects/pack directory' '
GOP=.git/objects/pack &&
rm -fr $GOP &&
git index-pack --stdin --keep=test <../test-3-${packname_3}.pack &&
- test -f $GOP/pack-${packname_3}.pack &&
+ test_path_is_file $GOP/pack-${packname_3}.pack &&
cmp $GOP/pack-${packname_3}.pack ../test-3-${packname_3}.pack &&
- test -f $GOP/pack-${packname_3}.idx &&
+ test_path_is_file $GOP/pack-${packname_3}.idx &&
cmp $GOP/pack-${packname_3}.idx ../test-3-${packname_3}.idx &&
- test -f $GOP/pack-${packname_3}.keep
+ test_path_is_file $GOP/pack-${packname_3}.keep
)
'
@@ -376,7 +376,7 @@ test_expect_success 'build pack index for an existing pack' '
rm -f test-4.keep &&
git index-pack --keep=why test-4.pack &&
cmp test-1-${packname_1}.idx test-4.idx &&
- test -f test-4.keep &&
+ test_path_is_file test-4.keep &&
:
'
@@ -616,7 +616,7 @@ test_expect_success 'setup: fake a SHA1 hash collision' '
cd corrupt &&
long_a=$(git hash-object -w ../a | sed -e "s!^..!&/!") &&
long_b=$(git hash-object -w ../b | sed -e "s!^..!&/!") &&
- test -f .git/objects/$long_b &&
+ test_path_is_file .git/objects/$long_b &&
cp -f .git/objects/$long_a \
.git/objects/$long_b
)
Range-diff against v1:
1: ca6cd5870e = 1: ca6cd5870e t5300: modernize test path checks in t5300
--
2.56.0.116.g6de20f6092.dirty
next prev parent reply other threads:[~2026-10-27 18:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 15:48 [Outreachy] Microproject: Modernize file check in t5300-pack-object.sh Ogundipe Sola Taiwo
2026-10-26 10:20 ` [PATCH] t5300: modernize test path checks in t5300 Ogundipe Sola Taiwo
2026-10-27 16:56 ` Usman Akinyemi
2026-10-26 20:32 ` [Outreachy] Microproject: Modernize file check in t5300-pack-object.sh Usman Akinyemi
2026-10-27 18:36 ` Ogundipe Sola Taiwo [this message]
2026-10-28 14:02 ` [PATCH v2] t5300: modernize test path checks in t5300 Usman Akinyemi
2026-10-28 14:12 ` Junio C Hamano
2026-10-27 18:42 ` [Outreachy] Microproject: Modernize file check in t5300-pack-object.sh Ogundipe Sola Taiwo
2026-10-29 11:48 ` Ogundipe Sola Taiwo
2026-10-29 12:02 ` [PATCH v3] t5300: modernize test path checks in t5300 Ogundipe Sola Taiwo
2026-10-29 18:36 ` Junio C Hamano
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=20261027183623.3600-1-ogundipesolataiwo12@gmail.com \
--to=ogundipesolataiwo12@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=siddharthasthana31@gmail.com \
--cc=usmanakinyemi202@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