You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Report doesn't contain something related to timings. I see "timestamp": "Sep 20, 2018 at 1:34pm", but what this means... report generation date... or when execution started...
I would like to see when exactly execution started and finished. Moreover please don't store formatted time, it would be easier to make 3rd party integrations.
The same for specs/scenarios/steps... We don't have timings, only duration.
"executionTime": "1002"
It's confusing. In terms of gauge it is duration in milliseconds.
@nvborisenko The timestamp that is shown is the time when execution started.
Your suggestions seem helpful to have. Although this is an issue in the html-report plugin and not directly related to Gauge core itself. I will be moving this issue there.
Also it would really help us if you could contribute this to Gauge through a PR.
From @nvborisenko on September 21, 2018 14:51
Report doesn't contain something related to timings. I see "timestamp": "Sep 20, 2018 at 1:34pm", but what this means... report generation date... or when execution started...
I would like to see when exactly execution started and finished. Moreover please don't store formatted time, it would be easier to make 3rd party integrations.
The same for specs/scenarios/steps... We don't have timings, only duration.
It's confusing. In terms of gauge it is duration in milliseconds.
Copied from original issue: getgauge/gauge#1189
The text was updated successfully, but these errors were encountered: