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,462,888
Community Members
 
Community Events
176
Community Groups

Xray Test Execution start time changed with every import

We are using Xray Test Executions to trigge jenkins pipelines for remote and scheduled test executions. The results are put together in a cucumber.json that we import into Xray once the test is finished.

While importing however the "started on" Field is overwritten with the current time completely ignoring the value of the "start_timestamp" in the .json file.

This results in all our tests having a runtime of 0 seconds which completely wrecks our statistics.

We would like to see the actual time we startetd the test and not the latest refresh.

 

Screenshot 1: Actual Runtime of Test Execution:

13896801.gif

 

Screenshot 2: Time started and finished13910996.gif

1 answer

1 vote

Hi @Simon-Sebastian Schreiner 

Unfortunately, the Cucumber JSON format does not provide dates for the start and finish of the scenarios.
So what we're currently doing is using the current date, assuming that the trigger (i.e., the moment whenever you submit the results) corresponds to the moment whenever they were run; in most cases, these dates will match. However, there can be a slight difference between the real start date and the "Started on" date shown on the screen; concerning the finish date, it's not accurate because currently, we don't take into account the sum of the duration of all steps.

Alternatively, you may use the Cucumber multipart endpoint. The information of the Start and Finish dates will be sent in a second file where you can set the values to Test Execution custom fields. So you're able to define the start and finish dates for the related Test Execution. For this, you would need to obtain the starting and finished dates in the CI side, to pass them into the task for submitting the cucumber multipart results.

If you have any additional questions you can reach out to our support for further investigation.

Best regards,

Team Xray 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events