308280e7a9
The original Ant JUnit reporter only writes <system-err> and <system-out> to the <testsuite>, but more modern reporters such as Maven Surefire scopes output to each individual <testcase>. This is also handled by both the Jenkins JUnit and xUnit plugins, e.g.: https://github.com/jenkinsci/junit-plugin/commit/145eb5c98 Pick-to: 6.2 Change-Id: I20c87276004a4e0910fc18e05e6ffa0f5e5a7b7c Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io> Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
18 lines
1.0 KiB
XML
18 lines
1.0 KiB
XML
<?xml version="1.0" encoding="UTF-8" ?>
|
|
<testsuite name="tst_BenchlibCounting" timestamp="@TEST_START_TIME@" hostname="@HOSTNAME@" tests="5" failures="1" errors="0" skipped="1" time="@TEST_DURATION@">
|
|
<properties>
|
|
<property name="QTestVersion" value="@INSERT_QT_VERSION_HERE@"/>
|
|
<property name="QtVersion" value="@INSERT_QT_VERSION_HERE@"/>
|
|
<property name="QtBuild" value=""/>
|
|
</properties>
|
|
<testcase name="initTestCase" classname="tst_BenchlibCounting" time="@TEST_DURATION@"/>
|
|
<testcase name="passingBenchmark" classname="tst_BenchlibCounting" time="@TEST_DURATION@"/>
|
|
<testcase name="skippingBenchmark" classname="tst_BenchlibCounting" time="@TEST_DURATION@">
|
|
<skipped message="This is a skipping benchmark"/>
|
|
</testcase>
|
|
<testcase name="failingBenchmark" classname="tst_BenchlibCounting" time="@TEST_DURATION@">
|
|
<failure type="fail" message="This is a failing benchmark"/>
|
|
</testcase>
|
|
<testcase name="cleanupTestCase" classname="tst_BenchlibCounting" time="@TEST_DURATION@"/>
|
|
</testsuite>
|