Closed ncariss closed 2 years ago
Hi @ncariss , to be able to help you out,
Hi @bitcoder ! Thanks for the quick reply!
We are using Xray Server+DC.
I created a minimum working example here. (Interestingly, mvn test does not find any tests, but running the tests using IntelliJ works. Apparently just including the xray-junit-extensions as a Maven dependency blocks Maven Surefire from finding any tests.)
The XML report and screenshots can also be found in the repo: TEST-junit-jupiter.xml Without evidence uploaded we can see the AssertionError (which is what we want):
When uploading evidence, the AssertionError is unfortunately replaced by the evidence filename/link:
Cheers Nick
Hi @ncariss , so it's a bug on Xray server/DC side. I've used your report and upload to a Xray cloud instance and it shows fine as you can see. Please reach out to Xray support team and report it (please provide the junit xml file you generate). You can say that the same file seems to work fine in Xray cloud as I've checked it. I'll close this issue here. Thanks for the feedback :)
Note: concerning mvn test
, not sure what is happening. I can't replicate it. Besides the workflows are running fine,
Hi Sergio! Thank you for the analysis! I will address this with the Xray support then. Regarding the Maven issues I am facing, I will ask some colleagues to try my repo and report back in another ticket, if I can pinpoint it to the extension.
I am currently doing some JUnit tests that compare very long Maps and Lists using custom Hamcrest matchers. The matchers describe the mismatch in detail once an assertion fails. If I use the Xray-JUnit-Extension to upload the results to Jira, we can see the description of the AssertionError in the TestRun of our Testcases (test type "generic").
If, however, I also add some files as TestRun evidence, all I see in the TestRun in Jira is the link to one of the files. Is this something that could potentially be fixed/changed in the extension or is this due to behaviour of Xray itself?