diff options
author | David Bremner <bremner@debian.org> | 2011-09-12 22:40:57 -0300 |
---|---|---|
committer | David Bremner <bremner@debian.org> | 2011-09-12 23:35:21 -0300 |
commit | 22af786838793ed97fa3dbb1d223e90602912b71 (patch) | |
tree | 06f5157537400795eae0e03f3a97ed110df359b2 /test/test-lib.sh | |
parent | fa52a0d094a6585f36f484082fc3e28261718e72 (diff) |
test: reset test_subtest_known_broken_ after each success/failure.
This means that test_subtest_known_broken needs to be called before
every known broken subtest, which is no different than what is
documented for the test_begin_subtest case.
The assumption is that every test ends up calling either skipping,
calling test_ok_ or test_failure_ and and the latter in turn delegate
to the known_broken versions in the case where
test_subtest_known_broken_ is set.
Diffstat (limited to 'test/test-lib.sh')
-rwxr-xr-x | test/test-lib.sh | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/test/test-lib.sh b/test/test-lib.sh index 196ef496..966b2dcf 100755 --- a/test/test-lib.sh +++ b/test/test-lib.sh @@ -574,12 +574,14 @@ test_failure_message_ () { } test_known_broken_ok_ () { + test_subtest_known_broken_= test_fixed=$(($test_fixed+1)) say_color pass "%-6s" "FIXED" echo " $@" } test_known_broken_failure_ () { + test_subtest_known_broken_= test_broken=$(($test_broken+1)) test_failure_message_ "BROKEN" "$@" } @@ -614,6 +616,7 @@ test_skip () { fi case "$to_skip" in t) + test_subtest_known_broken_= say_color skip >&3 "skipping test: $@" say_color skip "%-6s" "SKIP" echo " $1" |