You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the JUnit parser, the tests/failures/errors/skipped attributes on <testsuite> are ignored, instead the reported figures are decided by the number of <testcase> sub-elements. In my use case I don't want to add the passed tests to the XML, just the failed ones, but I would like to see the count of tests passed.
To Reproduce
This minimal XML report shows blanks in the Action output:
The Action report shows the specified counts from the <testsuite> element.
Screenshots
Additional context
The XML report is auto-generated by a utility which checks strings for validity and outputs JUnit-compatible format. There are about 2500 strings checked, I don't want to write 2500 <testcase> elements to the XML if possible. I have full access to the source for the utility so I can tweak the output format as needed.
Thanks for any feedback you can give!
The text was updated successfully, but these errors were encountered:
Describe the bug
Using the JUnit parser, the tests/failures/errors/skipped attributes on
<testsuite>
are ignored, instead the reported figures are decided by the number of<testcase>
sub-elements. In my use case I don't want to add the passed tests to the XML, just the failed ones, but I would like to see the count of tests passed.To Reproduce
This minimal XML report shows blanks in the Action output:
Expected behavior
The Action report shows the specified counts from the
<testsuite>
element.Screenshots
Additional context
The XML report is auto-generated by a utility which checks strings for validity and outputs JUnit-compatible format. There are about 2500 strings checked, I don't want to write 2500
<testcase>
elements to the XML if possible. I have full access to the source for the utility so I can tweak the output format as needed.Thanks for any feedback you can give!
The text was updated successfully, but these errors were encountered: