Files
tasks/tools/testrunner/testdata/junit-unexpected-call-failure.xml
Stephan BehnkeandGitHub e578494496 JUnit summary with failures (#9912)
## What changed?

Add failure details per test to GitHub summary view.

## Why?

Avoid digging through logs.

## How did you test it?
- [ ] built
- [ ] run locally and tested manually
- [ ] covered by existing tests
- [x] added new unit test(s)
- [ ] added new functional test(s)

**Example**:

<img width="1193" height="644" alt="Screenshot 2026-04-13 at 1 58 43 PM"
src="https://github.com/user-attachments/assets/9743dba8-7e66-42c9-a877-240e36d7b9b9"
/>

https://github.com/temporalio/temporal/actions/runs/24366106128?pr=9912
2026-04-16 16:16:57 +00:00

15 lines
548 B
XML

<testsuites tests="1" failures="1">
<testsuite name="MySuite" tests="1" failures="1" errors="0" id="0" time="">
<testcase name="TestBaz">
<failure message="Unexpected call" type="Failed"><![CDATA[=== RUN TestBaz
=== CONT TestBaz
helper.go:1: some setup log
mock_file.go:42: Unexpected call to SomeMethod(...)
expected call at foo_test.go:10 doesn't match argument at index 0.
Got: "actual"
Want: is equal to "expected"
FAIL]]></failure>
</testcase>
</testsuite>
</testsuites>