mirror of
https://github.com/jstemmer/go-junit-report.git
synced 2025-04-05 05:00:15 -05:00
46e0aed494
When we encounter a failure but there was not failing test, we create a failing dummy test in the report. This is to prevent the failure from being overlooked. The case where the output contained a failing benchmark was not handled correctly, resulting in a dummy test failure being added to the report unnecessarily.
22 lines
1020 B
XML
22 lines
1020 B
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<testsuites tests="3" failures="2" skipped="1">
|
|
<testsuite name="package/name/benchfail" tests="3" failures="2" errors="0" id="0" hostname="hostname" skipped="1" time="0.002" timestamp="2022-01-01T00:00:00Z">
|
|
<properties>
|
|
<property name="go.version" value="1.0"></property>
|
|
</properties>
|
|
<testcase name="BenchmarkError" classname="package/name/benchfail" time="0.000">
|
|
<failure message="Failed"><![CDATA[ bench_test.go:6: error message]]></failure>
|
|
</testcase>
|
|
<testcase name="BenchmarkFatal" classname="package/name/benchfail" time="0.000">
|
|
<failure message="Failed"><![CDATA[ bench_test.go:10: fatal message]]></failure>
|
|
</testcase>
|
|
<testcase name="BenchmarkSkip" classname="package/name/benchfail" time="0.000">
|
|
<skipped message="Skipped"><![CDATA[ bench_test.go:14: skip message]]></skipped>
|
|
</testcase>
|
|
<system-out><![CDATA[goos: linux
|
|
goarch: amd64
|
|
pkg: package/name/benchfail
|
|
exit status 1]]></system-out>
|
|
</testsuite>
|
|
</testsuites>
|