From: Andrei Rybak <rybak.a.v@gmail.com>
To: git@vger.kernel.org
Cc: "Patrick Steinhardt" <ps@pks.im>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Øystein Walle" <oystwa@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>
Subject: [PATCH v3 0/3] git config tests for "'git config ignores pairs ..."
Date: Sun, 23 Apr 2023 15:46:46 +0200 [thread overview]
Message-ID: <20230423134649.431783-1-rybak.a.v@gmail.com> (raw)
In-Reply-To: <20230418175034.982433-1-rybak.a.v@gmail.com>
Clean up existing tests and add new tests in t1300-config.sh.
v1 cover letter:
https://lore.kernel.org/git/20230414081352.810296-1-rybak.a.v@gmail.com/
v2 cover letter:
https://lore.kernel.org/git/20230418175034.982433-1-rybak.a.v@gmail.com/
Changes since v2:
- Patch 3 updates:
- Added missing word "are" in commit message
- Added signoff
- Wrapped $1 and $2 in double quotes for consistency with
`git grep -P 'local .*="?[$][1-9]"? &&$' -- t`
- Added &&-chainging to function "test_missing_key"
- Fixed quoting so that substitution of $key happens inside eval
- Added tests about config subsections
Changes since v1:
- Rewritten commit message for patch 2.
- New RFC patch 3.
Andrei Rybak (3):
t1300: drop duplicate test
t1300: check stderr for "ignores pairs" tests
t1300: add tests for missing keys
t/t1300-config.sh | 33 ++++++++++++++++++++++-----------
1 file changed, 22 insertions(+), 11 deletions(-)
Range diff against v2:
1: cf812f4fa8 = 1: cf812f4fa8 t1300: drop duplicate test
2: b4132adea8 = 2: b4132adea8 t1300: check stderr for "ignores pairs" tests
3: 6126f42449 ! 3: ba536bf855 t1300: add tests for missing keys
@@ Metadata
## Commit message ##
t1300: add tests for missing keys
- There several tests in t1300-config.sh that validate failing invocations
- of "git config". However, there are no tests that check what happens
- when "git config" is asked to retrieve a value for a missing key.
+ There are several tests in t1300-config.sh that validate failing
+ invocations of "git config". However, there are no tests that check
+ what happens when "git config" is asked to retrieve a value for a
+ missing key.
- Add tests that check this for various combinations of "<section>.<key>".
+ Add tests that check this for various combinations of "<section>.<key>"
+ and "<section>.<subsection>.<key>".
+
+ Signed-off-by: Andrei Rybak <rybak.a.v@gmail.com>
## t/t1300-config.sh ##
@@ t/t1300-config.sh: test_expect_success 'subsections are not canonicalized by git-config' '
@@ t/t1300-config.sh: test_expect_success 'subsections are not canonicalized by git
'
+test_missing_key () {
-+ local key=$1
-+ local title=$2
-+ test_expect_success "value for $title is not printed" "
-+ test_must_fail git config $key >out 2>err &&
++ local key="$1" &&
++ local title="$2" &&
++ test_expect_success "value for $title is not printed" '
++ test_must_fail git config "$key" >out 2>err &&
+ test_must_be_empty out &&
+ test_must_be_empty err
-+ "
++ '
+}
+
+test_missing_key 'missingsection.missingkey' 'missing section and missing key'
+test_missing_key 'missingsection.penguin' 'missing section and existing key'
+test_missing_key 'section.missingkey' 'existing section and missing key'
++test_missing_key 'section.MissingSubSection.missingkey' 'missing subsection and missing key'
++test_missing_key 'section.SubSection.missingkey' 'existing subsection and missing key'
++test_missing_key 'section.MissingSubSection.key' 'missing subsection and existing key'
+
cat > .git/config <<\EOF
[alpha]
--
2.40.0
next prev parent reply other threads:[~2023-04-23 13:47 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 21:28 [PATCH v1 0/6] t: fix unused files, part 2 Andrei Rybak
2023-04-01 21:28 ` [PATCH v1 1/6] t0300: don't create unused file Andrei Rybak
2023-04-02 1:30 ` Eric Sunshine
2023-04-01 21:28 ` [PATCH v1 2/6] t1300: fix config file syntax error descriptions Andrei Rybak
2023-04-01 21:28 ` [PATCH v1 3/6] t1300: don't create unused files Andrei Rybak
2023-04-01 21:28 ` [PATCH v1 4/6] t1450: " Andrei Rybak
2023-04-01 21:28 ` [PATCH v1 5/6] t1502: " Andrei Rybak
2023-04-01 21:28 ` [PATCH v1 6/6] t2019: " Andrei Rybak
2023-04-03 22:33 ` [PATCH v2 0/6] t: fix unused files, part 2 Andrei Rybak
2023-04-03 22:33 ` [PATCH v2 1/6] t0300: don't create unused file Andrei Rybak
2023-04-06 8:34 ` Ævar Arnfjörð Bjarmason
2023-04-06 21:01 ` Andrei Rybak
2023-04-03 22:33 ` [PATCH v2 2/6] t1300: fix config file syntax error descriptions Andrei Rybak
2023-04-03 22:33 ` [PATCH v2 3/6] t1300: don't create unused files Andrei Rybak
2023-04-06 8:38 ` Ævar Arnfjörð Bjarmason
2023-04-06 21:30 ` Andrei Rybak
2023-04-06 21:35 ` git config tests for "'git config ignores pairs ..." (was Re: [PATCH v2 3/6] t1300: don't create unused files) Andrei Rybak
2023-04-14 8:13 ` [PATCH v1 0/2] git config tests for "'git config ignores pairs ..." Andrei Rybak
2023-04-14 8:13 ` [PATCH v1 1/2] t1300: drop duplicate test Andrei Rybak
2023-04-14 8:13 ` [PATCH v1 2/2] t1300: check stderr for "ignores pairs" tests Andrei Rybak
2023-04-14 13:28 ` Andrei Rybak
2023-04-18 17:50 ` [PATCH v2 0/3] git config tests for "'git config ignores pairs ..." Andrei Rybak
2023-04-18 17:50 ` [PATCH v2 1/3] t1300: drop duplicate test Andrei Rybak
2023-04-18 18:37 ` Junio C Hamano
2023-04-18 17:50 ` [PATCH v2 2/3] t1300: check stderr for "ignores pairs" tests Andrei Rybak
2023-04-18 18:39 ` Junio C Hamano
2023-04-18 17:50 ` [RFC PATCH v2 3/3] t1300: add tests for missing keys Andrei Rybak
2023-04-18 19:31 ` Junio C Hamano
2023-04-18 17:53 ` [PATCH v2 0/3] git config tests for "'git config ignores pairs ..." Andrei Rybak
2023-04-23 13:46 ` Andrei Rybak [this message]
2023-04-23 13:46 ` [PATCH v3 1/3] t1300: drop duplicate test Andrei Rybak
2023-04-23 13:46 ` [PATCH v3 2/3] t1300: check stderr for "ignores pairs" tests Andrei Rybak
2023-04-23 13:46 ` [PATCH v3 3/3] t1300: add tests for missing keys Andrei Rybak
2023-05-01 22:02 ` [PATCH v3 0/3] git config tests for "'git config ignores pairs ..." Junio C Hamano
2023-05-02 19:58 ` Andrei Rybak
2023-04-03 22:33 ` [PATCH v2 4/6] t1450: don't create unused files Andrei Rybak
2023-04-06 8:41 ` Ævar Arnfjörð Bjarmason
2023-04-06 22:19 ` Andrei Rybak
2023-04-03 22:33 ` [PATCH v2 5/6] t1502: " Andrei Rybak
2023-04-06 8:15 ` Øystein Walle
2023-04-06 8:47 ` Ævar Arnfjörð Bjarmason
2023-04-06 19:51 ` Andrei Rybak
2023-04-03 22:33 ` [PATCH v2 6/6] t2019: " Andrei Rybak
2023-04-06 8:44 ` Ævar Arnfjörð Bjarmason
2023-04-07 2:19 ` Andrei Rybak
2023-04-08 20:54 ` [PATCH] t2024: fix loose/strict local base branch DWIM test Andrei Rybak
2023-04-10 17:37 ` Junio C Hamano
2023-04-17 19:10 ` [PATCH v3 0/6] t: fix unused files, part 2 Andrei Rybak
2023-04-17 19:10 ` [PATCH v3 1/6] t0300: don't create unused file Andrei Rybak
2023-04-17 19:10 ` [PATCH v3 2/6] t1300: fix config file syntax error descriptions Andrei Rybak
2023-04-17 19:10 ` [PATCH v3 3/6] t1300: don't create unused files Andrei Rybak
2023-04-17 19:10 ` [PATCH v3 4/6] t1450: " Andrei Rybak
2023-04-17 19:10 ` [PATCH v3 5/6] t1502: " Andrei Rybak
2023-04-17 19:10 ` [PATCH v3 6/6] t2019: " Andrei Rybak
2023-05-01 21:52 ` [PATCH v3 0/6] t: fix unused files, part 2 Junio C Hamano
2023-05-02 21:03 ` Andrei Rybak
2023-05-03 4:11 ` Elijah Newren
2023-05-03 15:54 ` 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=20230423134649.431783-1-rybak.a.v@gmail.com \
--to=rybak.a.v@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=oystwa@gmail.com \
--cc=ps@pks.im \
/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).