From a4e4436e852c600a7ecd13b83fc487164dbc5ad7 Mon Sep 17 00:00:00 2001 From: Mitch Curtis Date: Wed, 2 Sep 2020 14:37:20 +0200 Subject: [PATCH] Doc: explain how to blacklist QML tests on certain platforms Change-Id: Icd505175805820c64593d7eb8f580a51008e2e1a Pick-to: 5.15 5.12 Reviewed-by: Daniel Smith --- src/testlib/qtestblacklist.cpp | 22 ++++++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/src/testlib/qtestblacklist.cpp b/src/testlib/qtestblacklist.cpp index 6695605f122..b9d174bbe06 100644 --- a/src/testlib/qtestblacklist.cpp +++ b/src/testlib/qtestblacklist.cpp @@ -88,9 +88,27 @@ QT_BEGIN_NAMESPACE [testfunction2:testData] msvc-2010 + QML test functions are identified using the following format: + + ::: + + For example, to blacklist a QML test on RHEL 7.6: + + # QTBUG-12345 + [Button::test_display:TextOnly] + ci rhel-7.6 + Keys are lower-case. Distribution name and version are supported if - QSysInfo's productType() and productVersion() return them. Keys can be - added via the space-separated QTEST_ENVIRONMENT environment variable. + QSysInfo's productType() and productVersion() return them. + + Keys can be added via the space-separated QTEST_ENVIRONMENT + environment variable: + + QTEST_ENVIRONMENT=ci ./tst_stuff + + This can be used to "mock" a test environment. In the example above, + we add "ci" to the list of keys for the test environment, making it + possible to test BLACKLIST files that blacklist tests in a CI environment. The other known keys are listed below: */