Closed mikz closed 1 year ago
Right, that was some special logic coming from JUnit files. Maybe this should be generalized and case.message
and case.content
should always be used.
I think this has to be fixed in a different place. That message is used to identify identical test cases. The message used in the annotations is defined elsewhere, and should be changed there.
I have created a fix, please test the fix as follows (includes fix for #354):
uses: EnricoMi/publish-unit-test-result-action/composite@branch-stdout-and-stderr
This has been fixed in #358.
Given the following example XML:
The GitHub check should show
Zenject.ZenjectException : Zenject Validation Failed! See errors below for details.
plus the stack trace. But it just shows the stack trace.The junit
<failure message=""
should be set correctly with this transform: https://github.com/EnricoMi/publish-unit-test-result-action/blob/60624fdd8b1c397574bea72453e03235683eca86/python/publish/xslt/nunit3-to-junit.xslt#L118-L120But somehow it still does not appear on GitHub.