Details
-
Improvement
-
Status: Waiting Approval
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
-
XRAY 2020 Sprint 7
-
Description
Currently, only the text in the <failure> message is processed/imported. The "message" attribute on the <failure> element should also be imported.
The same applies for the <error> element.
https://github.com/windyroad/JUnit-Schema/blob/master/JUnit.xsd
Examples:
<testcase classname='XCUITest101UITests.XCUITest101UITests' name='testRecorded'> <failure message='Failed to get matching snapshot: Multiple matching elements found for <XCUIElementQuery: 0x60000380eda0>.'>XCUITest101UITests.swift:25</failure> </testcase>
<testcase name="CanAddNumbers" classname="com.xpand.java.CalcTest" time="0.005"> <failure message=" Expected: is <2> but: was <0>" type="java.lang.AssertionError"><![CDATA[java.lang.AssertionError: Expected: is <2> but: was <0> at com.xpand.java.CalcTest.CanAddNumbers(CalcTest.java:26) ]]></failure> </testcase>
Attachments
Issue Links
- relates to
-
XRAY-4993 As system, debug/output information on JUnit XML reports should be imported to the Test Run
- Gathering Interest
-
XRAYCLOUD-1520 As system, debug/output information on JUnit XML reports should be imported to the Test Run
- Gathering Interest
-
XRAY-2418 As system, whenever importing JUnit results, the "stdout" message should be appended to the Error Message information shown in the execution screen
- New