One test in t1308 expects test-config to fail with exit code 128 due to
a parsing error in the config machinery. But test-config might also exit
with 128 for any other reason that leads it to call die(). Therefore the
test can potentially succeed for the wrong reason. To avoid false
positives, let's check test-config's output, in addition to the exit
code, and make sure that the cause of the error is the one we expect in
this test.
Moreover, the test was using the auxiliary function check_config which
optionally takes a string to compare the test-config stdout against.
Because this string is optional, there is a risk that future callers may
also check only the exit code and not the output. To avoid that, make
the string parameter of this function mandatory.
Signed-off-by: Matheus Tavares <matheus.bernardino@xxxxxx>
---
t/t1308-config-set.sh | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/t/t1308-config-set.sh b/t/t1308-config-set.sh
index 3a527e3a84..cff17120dc 100755
--- a/t/t1308-config-set.sh
+++ b/t/t1308-config-set.sh
@@ -14,10 +14,7 @@ check_config () {
expect_code=0
fi &&
op=$1 key=$2 && shift && shift &&
- if test $# != 0
- then
- printf "%s\n" "$@"
- fi >expect &&
+ printf "%s\n" "$@" >expect &&
test_expect_code $expect_code test-tool config "$op" "$key" >actual &&
test_cmp expect actual
}
@@ -130,7 +127,8 @@ test_expect_success 'check line error when NULL string is queried' '
'
test_expect_success 'find integer if value is non parse-able' '
- check_config expect_code 128 get_int lamb.head
+ test_expect_code 128 test-tool config get_int lamb.head 2>result &&
+ test_i18ngrep "fatal: bad numeric config value '\'none\'' for '\'lamb.head\''" result
'
test_expect_success 'find bool value for the entered key' '
--
2.28.0
