1berry/qtbase
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Doc: explain how to blacklist QML tests on certain platforms

Browse Source 
Change-Id: Icd505175805820c64593d7eb8f580a51008e2e1a
Reviewed-by: Daniel Smith <Daniel.Smith@qt.io>
(cherry picked from commit a4e4436e852c600a7ecd13b83fc487164dbc5ad7)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This commit is contained in:
Mitch Curtis 2020-09-02 14:37:20 +02:00 committed by Qt Cherry-pick Bot
parent 80c3d4a20a
commit 7a7996beb5
1 changed files with 20 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
src/testlib/qtestblacklist.cpp
View File

@ -87,9 +87,27 @@ QT_BEGIN_NAMESPACE
[testfunction2:testData] [testfunction2:testData]
msvc-2010 msvc-2010
QML test functions are identified using the following format:
<TestCase name>::<function name>:<data tag>
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 Keys are lower-case. Distribution name and version are supported if
QSysInfo's productType() and productVersion() return them. Keys can be QSysInfo's productType() and productVersion() return them.
added via the space-separated QTEST_ENVIRONMENT environment variable.
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: The other known keys are listed below:
*/ */