Xray import JUnit results from tests but it creates different test issues

[Azahara Camacho]

Hello,

I am trying to import the results of my test plan execution to Xray, but I have some troubles. I list you the steps that I follow to reproduce it:

1. I create test Cucumber issues that I export after this for its development in my project. I get all the tags of the stories covered with them and the test plan where I collect them.
2. After completing them, I generate a JUnit XML report.
3. I import it to Xray.
   • The results are imported to the correct Test Execution and Test Plan, but the test issues are not updated with the execution results.
   • Other test issues are created as "Generic" with the name "(Epic name): (name of the original test issue)" and the original test issues are not modified. Finally, I get the same amount of new test issues than the original ones that I tested.

Could you help me with this problem?

Thanks!

[Sergio Freire - Xblend · Accepted solution]

Hi @Azahara Camacho

For guidance, you can check our support documentation regarding this topic: 

• Taking advantage of JUnit XML reports;
• Examples using JUnit

If your doubts remain, I recommend you to reach out Xray support and the team will be glad to help you out.

Best Regards,

Sergio

Solution Architect and Testing Advocate @Xray

Personal blog on testing, Agile, and software development: https://sergiofreire.com

Follow me on Twitter: https://twitter.com/darktelecom

[Ashok Dalabehera · Accepted solution]

Hi, This is Ashok Dalabehera. I am also facing the exact problem.

[Srinivasan Anantharaman]

Hi @Ashok Dalabehera - Ending up in the exact same scenario of duplicate test issues being created. Ours is a custom junit xml and trying to figure out what is being missed. Any hints on how this issue was resolved at your end? Thank You.

[Stefan Salzl]

@Azahara Camacho , @Srinivasan Anantharaman , @Ashok Dalabehera :

Is there still an issue with this?

Best
Stefan

[Srinivasan Anantharaman]

@Stefan Salzl 

Adapting a workaround process by mapping “issuekey” field during upload to avoid  duplicate issues being created. Requires jira-admin rights :) 

[Stefan Salzl]

that sounds interesting. Would you mind to describe the workaround here?

Best
Stefan

[Srinivasan Anantharaman]

Not sure if yours is the same use case. Anyways, Please refer the solution to 

Solved: Generic tests from automated code (Xray) updated c... (atlassian.com)

Note: Updated the link.