tests: never source test-defs.sh directly, source test-lib.sh instead
authorStefano Lattarini <stefano.lattarini@gmail.com>
Thu, 26 Jul 2012 10:50:32 +0000 (12:50 +0200)
committerStefano Lattarini <stefano.lattarini@gmail.com>
Thu, 26 Jul 2012 12:11:40 +0000 (14:11 +0200)
commitf2b8b7659ae48941ab0be64d1663dd673e097d58
treeb4f89923c6d3bda7b705f7109928474a0141a6b1
parentdb188c29be11177499d4c96bd2b8327e884f7d8c
tests: never source test-defs.sh directly, source test-lib.sh instead

After the recent re-organization, sourcing 'test-defs.sh' directly might
not work well and cause spurious failures or other unexpected behaviours.
We should source 'test-lib.sh' instead, which contains not more direct
code execution (only definition of shell variables/functions, or sourcing
of other '*.sh' with the same property), is protected against multiple
inclusions, and sources 'test-defs.sh' automatically in in a proper way.

* t/testsuite-summary-count.sh, t/tap-summary.sh, t/tap-summary-color.sh,
t/testsuite-summary-color.sh: Source 'test-lib.sh', not 'test-defs.sh'.
* gen-testsuite-part: Likewise, in the generated wrapper scripts.

Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>
gen-testsuite-part
t/tap-summary-color.sh
t/tap-summary.sh
t/testsuite-summary-color.sh
t/testsuite-summary-count.sh