Please add another vote for supporting milliseconds for the elapsed time field in test results. I hope your new Jenkins integration will support test case run times in milliseconds.
Added, thanks Barbara
Please add another vote for millisecond support!
Please add a vote for us also.
Just for reference, where is this request in the priority list?
We currently don’t have an estimate for this feature but I’m happy to add another vote, thanks for your feedback! We prioritize feature requests (and group them into smaller, mid-size and bigger features) but don’t have a formal prioritization process. We review the open feature requests for every release and typically combine multiple related feature requests into the same release (“themed” releases).
Please, add also my vote too
Thanks for your feedback, Maurizio
Another vote for millisecond support. We want to track elapsed time for API calls which are mostly less than 1 second. While we could add a custom field (or use an external repository) for this, we’d much prefer to use the built-in field.
Thanks for your feedback, @autobot! We would recommend rounding to the nearest second in this case but I understand that milliseconds would be more accurate/convenient in this case.
Please add support for milliseconds for elapsed. 1 second is a ridiculously high minimum value for a test.
Thanks for your feedback, Kip!
I agree with Kip. Please add support for milliseconds for elapsed and estimate-fields.
Adding my vote for elapsed time millisecond support as well. It would be very helpful!
Thanks for your feedback, I’ve added your vote to the request as well!
Please add another vote for millisecond support! More and more teams are implementing automation and this needs to get prioritized.