Doc: explain how to blacklist QML tests on certain platforms
Change-Id: Icd505175805820c64593d7eb8f580a51008e2e1a Pick-to: 5.15 5.12 Reviewed-by: Daniel Smith <Daniel.Smith@qt.io>
This commit is contained in:
parent
4f658d04da
commit
a4e4436e85
@ -88,9 +88,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:
|
||||||
*/
|
*/
|
||||||
|
Loading…
x
Reference in New Issue
Block a user