qt5base-lts/tests/auto/testlib/selftests/expected_tuplediagnostics.junitxml
Tor Arne Vestbø 308280e7a9 testlib: Move stdout/stderr reporting into individual <testcase> elements
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>
2021-08-10 18:06:36 +02:00

24 lines
1.3 KiB
XML

<?xml version="1.0" encoding="UTF-8" ?>
<testsuite name="tst_TupleDiagnostics" timestamp="@TEST_START_TIME@" hostname="@HOSTNAME@" tests="5" failures="2" errors="0" skipped="0" 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_TupleDiagnostics" time="@TEST_DURATION@"/>
<testcase name="testEmptyTuple" classname="tst_TupleDiagnostics" time="@TEST_DURATION@"/>
<testcase name="testSimpleTuple" classname="tst_TupleDiagnostics" time="@TEST_DURATION@">
<failure type="fail" message="Compared values are not the same">
<![CDATA[ Actual (std::tuple<int>{1}): std::tuple(1)
Expected (std::tuple<int>{2}): std::tuple(2)]]>
</failure>
</testcase>
<testcase name="testTuple" classname="tst_TupleDiagnostics" time="@TEST_DURATION@">
<failure type="fail" message="Compared values are not the same">
<![CDATA[ Actual (tuple1): std::tuple(42, 'Y', "tuple1")
Expected (tuple2): std::tuple(42, 'Y', "tuple2")]]>
</failure>
</testcase>
<testcase name="cleanupTestCase" classname="tst_TupleDiagnostics" time="@TEST_DURATION@"/>
</testsuite>