qt5base-lts/tests/auto/testlib/selftests/expected_benchlibcounting.junitxml

<?xml version="1.0" encoding="UTF-8" ?>
<testsuite errors="1" failures="1" tests="5" name="tst_BenchlibCounting">
  <properties>
    <property value="@INSERT_QT_VERSION_HERE@" name="QTestVersion"/>
    <property value="@INSERT_QT_VERSION_HERE@" name="QtVersion"/>
    <property value="" name="QtBuild"/>
  </properties>
  <testcase result="pass" name="initTestCase"/>
  <testcase result="pass" name="passingBenchmark">
  </testcase>
  <testcase name="skippingBenchmark">
    <!-- message="This is a skipping benchmark" type="skip" -->
  </testcase>
  <testcase result="fail" name="failingBenchmark">
    <failure message="This is a failing benchmark" result="fail"/>
  </testcase>
  <testcase result="pass" name="cleanupTestCase"/>
  <system-err>
<![CDATA[This is a skipping benchmark]]>
  </system-err>
</testsuite>
testlib: Report one test result per benchmark test. Prior to this commit, a benchmark test could report 0..n passes and 0..m fails or skips, where n is the number of accumulation iterations used to collect benchmark data and m is the number of times the test function was invoked. Depending on the type of benchmark measurer being used, this could result in a very large volume of test output and inconsistent pass, fail and skip counts between test runs. This commit changes the behaviour so that each benchmark test reports one pass, fail or skip, regardless of the number of iterations used to collect benchmark data. This commit also prevents benchmark data being reported in the test output if the benchmark test failed or skipped, as any benchmark data is of dubious value in such cases. The latter change in behaviour requires a minor modification to the badxml selftest, which now tests quoting of literal strings in xml test output for both passing and failing benchmarks. Finally, this commit also adds a new selftest specifically for verifying correct behaviour for benchmarks that fail or skip. Task-number: QTBUG-24313 Change-Id: I3426dc659a7511b62fd183a031c7235bc753f497 Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com> 2012-02-17 03:39:30 +00:00			`<?xml version="1.0" encoding="UTF-8" ?>`
			`<testsuite errors="1" failures="1" tests="5" name="tst_BenchlibCounting">`
			`<properties>`
			`<property value="@INSERT_QT_VERSION_HERE@" name="QTestVersion"/>`
			`<property value="@INSERT_QT_VERSION_HERE@" name="QtVersion"/>`
Use new QLibraryInfo::build() in testlib to log build information. This produces: ******* Start testing of tst_QtJson ******* Config: Using QtTest library 5.3.0, Qt 5.3.0 (Feb 13 2014, GCC 4.6.3, 64 bit, debug build) PASS : tst_QtJson::initTestCase() <?xml version="1.0" encoding="UTF-8"?> <TestCase name="tst_QtJson"> <Environment> <QtVersion>5.3.0</QtVersion> <QtBuild>Qt 5.3.0 (Feb 13 2014, GCC 4.6.3, 64 bit, debug build)</QtBuild> <QTestVersion>5.3.0</QTestVersion> </Environment> <?xml version="1.0" encoding="UTF-8" ?> <testsuite errors="1" failures="1" tests="42" name="tst_QtJson"> <properties> <property value="5.3.0" name="QTestVersion"/> <property value="5.3.0" name="QtVersion"/> <property value="Qt 5.3.0 (Feb 13 2014, GCC 4.6.3, 64 bit, debug build)" name="QtBuild"/> </properties> <Environment> <QtVersion>5.3.0</QtVersion> <QtBuild>Qt 5.3.0 (Feb 13 2014, GCC 4.6.3, 64 bit, debug build)</QtBuild> <QTestVersion>5.3.0</QTestVersion> </Environment> [ChangeLog][QtTest] Tests now output build information. Change-Id: I0ab473371575f2b807db725256805b8bffea3454 Reviewed-by: Sergio Ahumada <sahumada@blackberry.com> Reviewed-by: Jędrzej Nowacki <jedrzej.nowacki@digia.com> 2014-02-26 16:12:45 +00:00			`<property value="" name="QtBuild"/>`
testlib: Report one test result per benchmark test. Prior to this commit, a benchmark test could report 0..n passes and 0..m fails or skips, where n is the number of accumulation iterations used to collect benchmark data and m is the number of times the test function was invoked. Depending on the type of benchmark measurer being used, this could result in a very large volume of test output and inconsistent pass, fail and skip counts between test runs. This commit changes the behaviour so that each benchmark test reports one pass, fail or skip, regardless of the number of iterations used to collect benchmark data. This commit also prevents benchmark data being reported in the test output if the benchmark test failed or skipped, as any benchmark data is of dubious value in such cases. The latter change in behaviour requires a minor modification to the badxml selftest, which now tests quoting of literal strings in xml test output for both passing and failing benchmarks. Finally, this commit also adds a new selftest specifically for verifying correct behaviour for benchmarks that fail or skip. Task-number: QTBUG-24313 Change-Id: I3426dc659a7511b62fd183a031c7235bc753f497 Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com> 2012-02-17 03:39:30 +00:00			`</properties>`
			`<testcase result="pass" name="initTestCase"/>`
			`<testcase result="pass" name="passingBenchmark">`
			`</testcase>`
			`<testcase name="skippingBenchmark">`
			`<!-- message="This is a skipping benchmark" type="skip" -->`
			`</testcase>`
			`<testcase result="fail" name="failingBenchmark">`
			`<failure message="This is a failing benchmark" result="fail"/>`
			`</testcase>`
			`<testcase result="pass" name="cleanupTestCase"/>`
			`<system-err>`
			`<![CDATA[This is a skipping benchmark]]>`
			`</system-err>`
			`</testsuite>`