9b2971cbb4
For data-driven tests, testlib previously counted one fail or skip for each data row that failed or skipped, while it counted only one pass for a test function where all rows passed and counted no passes for a test function where some rows passed and some rows failed. A similar problem also existed for benchmark tests, which could run multiple iterations of the same test, with each fail and skip being counted but only a single pass being counted for the entire series of iterations. This commit makes testlib count one pass, fail or skip for each data row. Test functions that are not data-driven count one result for the test function, as before. Benchmark tests count one pass, fail or skip per iteration. A side-effect of this change is that the test output in plain text, xml and light xml formats now shows a result for every data row and benchmark iteration executed, allowing post-processors to correctly calculate the total number of tests executed. Previously, individual rows were not shown in the test output if they passed, making such calculations impossible. The only change to the xunitxml output format is to correct a bug where no test result was recorded for a test function if the last data row was skipped and all other rows passed -- in which case the overall result should be a pass. Note that there is also a pre-existing bug in the xunit logger, where no result is reported if all rows are skipped; that bug is unaffected by this commit. Task-number: QTBUG-21848 Task-number: QTBUG-22124 Change-Id: I7e17177e10d6e89e55b9684c159bd506f21d002b Reviewed-by: Ed Baak <ed.baak@nokia.com>
28 lines
1.4 KiB
Plaintext
28 lines
1.4 KiB
Plaintext
********* Start testing of tst_BenchlibEventCounter *********
|
|
Config: Using QTest library @INSERT_QT_VERSION_HERE@, Qt @INSERT_QT_VERSION_HERE@
|
|
PASS : tst_BenchlibEventCounter::initTestCase()
|
|
PASS : tst_BenchlibEventCounter::events(0)
|
|
RESULT : tst_BenchlibEventCounter::events():"0":
|
|
0 events per iteration (total: 0, iterations: 1)
|
|
PASS : tst_BenchlibEventCounter::events(1)
|
|
RESULT : tst_BenchlibEventCounter::events():"1":
|
|
1 events per iteration (total: 1, iterations: 1)
|
|
PASS : tst_BenchlibEventCounter::events(10)
|
|
RESULT : tst_BenchlibEventCounter::events():"10":
|
|
10 events per iteration (total: 10, iterations: 1)
|
|
PASS : tst_BenchlibEventCounter::events(100)
|
|
RESULT : tst_BenchlibEventCounter::events():"100":
|
|
100 events per iteration (total: 100, iterations: 1)
|
|
PASS : tst_BenchlibEventCounter::events(500)
|
|
RESULT : tst_BenchlibEventCounter::events():"500":
|
|
500 events per iteration (total: 500, iterations: 1)
|
|
PASS : tst_BenchlibEventCounter::events(5000)
|
|
RESULT : tst_BenchlibEventCounter::events():"5000":
|
|
5,000 events per iteration (total: 5,000, iterations: 1)
|
|
PASS : tst_BenchlibEventCounter::events(100000)
|
|
RESULT : tst_BenchlibEventCounter::events():"100000":
|
|
100,000 events per iteration (total: 100,000, iterations: 1)
|
|
PASS : tst_BenchlibEventCounter::cleanupTestCase()
|
|
Totals: 9 passed, 0 failed, 0 skipped
|
|
********* Finished testing of tst_BenchlibEventCounter *********
|