From dfbb2d6e1db3f23c89c0b09ef32fd886b176e4b8 Mon Sep 17 00:00:00 2001 From: Edward Welbourne Date: Tue, 10 Aug 2021 12:28:42 +0200 Subject: Clarify documentation of QEXPECT_FAIL()'s mode MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Present behavior is to continue or abort, according to the mode, regardless of whether the condition marked does fail. Change-Id: I2eb5eefbbf173326101d08f3bbb378d214e93e71 Reviewed-by: Tor Arne Vestbø Reviewed-by: Paul Wicking --- src/testlib/doc/src/qttestlib-manual.qdoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/testlib/doc') diff --git a/src/testlib/doc/src/qttestlib-manual.qdoc b/src/testlib/doc/src/qttestlib-manual.qdoc index 9073cc7c88..ff02ab876d 100644 --- a/src/testlib/doc/src/qttestlib-manual.qdoc +++ b/src/testlib/doc/src/qttestlib-manual.qdoc @@ -921,8 +921,8 @@ QSKIP can be used to skip testing when the implementation is not yet complete or not supported on a certain platform. When there are known - failures, it is recommended to use QEXPECT_FAIL, so that the test is - always completely executed. + failures, QEXPECT_FAIL is recommended, as it supports running the rest + of the test, when possible. Example of QSKIP in a test function: -- cgit v1.2.3