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

Next challenges

Recent achievements

Recognition

  • Give kudos
  • My kudos

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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
Community showcase
Published in Marketplace Apps & Integrations

5 mobile apps for Jira Cloud to boost productivity

  It’s very important to have access to the workflow process from anywhere. Especially if you manage the work of others. There is no difference whether you’re out of office, or drive a ca...

284 views 2 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you