| commit | 2958bb18c166468848d7046e04fbfcb3daba447e | |
| author | Luc Van Oostenryck <luc.vanoostenryck@gmail.com> | |
| Sun, 12 Feb 2017 23:28:56 +0000 (13 00:28 +0100) | ||
| committer | Christopher Li <sparse@chrisli.org> | |
| Mon, 13 Feb 2017 01:38:12 +0000 (13 09:38 +0800) | ||
| tree | c3aee97940c6117bdcd9045202aced98f2ceb2f3 | treesnapshot (tar.gz zip) |
| parent | 9ab8a6a72c38f5fc3d4cb3f2a403f9ab83c3206f | commitdiff |
testsuite: report as error tests known to fail but which succeed
Such situation may simply show that what was tested is now fixed
and that it's juste the test annotation which need to be adapted,
but can be a sign that something else is broken.
Reporting the exact result (failure/success, known-to-fail/expect-to-succeed)
make the testsuite more useful and allow to use more efficiently
git-bisect or other automated testing tools.
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Signed-off-by: Christopher Li <sparse@chrisli.org>
Such situation may simply show that what was tested is now fixed
and that it's juste the test annotation which need to be adapted,
but can be a sign that something else is broken.
Reporting the exact result (failure/success, known-to-fail/expect-to-succeed)
make the testsuite more useful and allow to use more efficiently
git-bisect or other automated testing tools.
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Signed-off-by: Christopher Li <sparse@chrisli.org>
| validation/test-suite | diffblobblamehistory |