On Thu, Mar 8, 2018 at 7:51 PM, Eric Sunshine <[email protected]> wrote:
> On Thu, Mar 8, 2018 at 7:38 AM, SZEDER Gábor <[email protected]> wrote:
>> Unroll that for loop, so we can check the files' contents the usual
>> way and rely on 'test_cmp's exit code failing the && chain. Extract
>> updating a file via CVS and verifying its contents using 'test_cmp'
>> into a helper function requiring the file's name as parameter to avoid
>> much of the repetition resulting from unrolling the loop.
>
> An alternative approach used elsewhere in the test suite[1] would be
> simply to 'exit' if test_cmp fails:
>
> for i in merge no-lf empty really-empty; do
> GIT_CONFIG="$git_config" cvs update -p "$i" >$i.out
> test_cmp $i.out ../$i || exit 1
> done &&
>
> (And, like the existing patch, this removes the need for capturing
> test_cmp's output into a "failures" file.)
>
> [1]: For example, the "setup" test of t2204-add-ignored.sh.
But 't/README' sayeth:
Don't:
- exit() within a <script> part.
And it's right: 'exit' terminates the shell process it's invoked in,
i.e. the whole test script (well, unless it's invoked in a subshell)
without executing the remaining tests and the usual housekeeping and
reporting.
Consider the following test script:
-- >8 --
#!/bin/sh
test_description='exit 1?'
. ./test-lib.sh
test_expect_success 'exit 1' '
exit 1
'
test_expect_success 'second test' '
true
'
test_done
-- >8 --
It's output:
$ ./t9999-exit.sh
FATAL: Unexpected exit with code 1
$ sed -e 's/exit 1/false/' -i t9999-exit.sh
$ ./t9999-exit.sh not ok 1 - false
#
# false
#
ok 2 - second test
# failed 1 among 2 test(s)
1..2
