10414444e1
We need to have a finer grained control over the tests we skip in our CI system. This adds a blacklisting mechanism that allows blacklisting individual test functions (or even test data) using a set of predefined matching keys for the operating system and some other relevant variables. QTestlib will search for a file called BLACKLIST in the test directory and parse it if found. The file contains a simple ini style list of functions to blacklist. For details see qtestblacklist.cpp. Change-Id: Id3fae4b264ca99970cbf9f45bfb85fa75c1fd823 Reviewed-by: Lars Knoll <lars.knoll@digia.com>
10 lines
568 B
Plaintext
10 lines
568 B
Plaintext
********* Start testing of tst_BenchlibCallgrind *********
|
|
Config: Using QtTest library @INSERT_QT_VERSION_HERE@, Qt @INSERT_QT_VERSION_HERE@
|
|
PASS : tst_BenchlibCallgrind::initTestCase()
|
|
PASS : tst_BenchlibCallgrind::twoHundredMillionInstructions()
|
|
RESULT : tst_BenchlibCallgrind::twoHundredMillionInstructions():
|
|
200,000,158 instruction reads per iteration (total: 200,000,158, iterations: 1)
|
|
PASS : tst_BenchlibCallgrind::cleanupTestCase()
|
|
Totals: 3 passed, 0 failed, 0 skipped, 0 blacklisted
|
|
********* Finished testing of tst_BenchlibCallgrind *********
|