Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,551,676
Community Members
 
Community Events
184
Community Groups

Problem with Xray import execution JUnit XML - Return empty array

Denise Cristina De Oliveira Maia Ribeiro
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Apr 03, 2023
We have running into a problem in Xray REST API that import execution results (JUnit xml) since last week (March 29th), before this date everything was working perfectly and we didn’t change anything in the code. I also checked the official documentation and nothing was changed since we started to use it.
When I’m calling the request:
curl -v --location -k --request POST 'https://xray.cloud.getxray.app/api/v1/import/execution/junit/multipart' -H "Authorization: Bearer $TOKEN_XRAY" -H "Content-Type: multipart/form-data" -F testInfo=@test_case_fields.json -F info=@test_execution_fields.json -F results=@target/surefire-reports/report_merged.xml
The response didn’t return the test execution key anymore but returns an empty body with status code 200. As I said, the XML and JSON files maintained in the same format as before (the last time that the script worked was in March 28th). I also tried to use REST API v2 and the same problem happened. Please, help us how to solve it because it is impacting our test results and reports.
Following the JSON files that we are using:

test_case_fields.json (testInfo):
{"fields":{"project":{"key":"CQA"},"labels":["Bugbash"],"customfield_11569":["FUNCTIONAL"],"customfield_11554":["FTS"]}}

test_execution_fields.json (info): {"fields":{"project":{"key":"CQA"},"summary":"[API]-Automation-contextual_search_v2","issuetype":{"name":"Test Execution"},"customfield_11566":["Automation"],"labels":["Bugbash"]},"xrayFields":{"testPlanKey":"CQA-608"}} 

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events