Include timings

[johnterickson]

Include timings

[mathstuf]

It looks like cargo might need to provide this information first :/ .

[svenstaro]

Seems it includes it just fine in the JSON output:

{ "type": "suite", "event": "ok", "passed": 15, "failed": 0, "allowed_fail": 0, "ignored": 0, "measured": 0, "filtered_out": 0, "exec_time": 0.219172866 }

[mathstuf]

I was thinking about per-test timings, not test suite level timings.

[svenstaro]

Well, it would be a start though.

[svenstaro]

Actually, we can get the per-test timings just fine: -Z unstable-options --format json --report-time

{ "type": "suite", "event": "started", "test_count": 2 }
{ "type": "test", "event": "started", "name": "can_get_health" }
{ "type": "test", "event": "started", "name": "can_get_index" }
{ "type": "test", "name": "can_get_health", "event": "ok", "exec_time": 0.039503535 }
{ "type": "test", "name": "can_get_index", "event": "ok", "exec_time": 0.029446912 }
{ "type": "suite", "event": "ok", "passed": 2, "failed": 0, "allowed_fail": 0, "ignored": 0, "measured": 0, "filtered_out": 0, "exec_time": 0.044548753 }

[svenstaro]

Actually it seems to just work already in cargo2junit: -Z unstable-options --format json --report-time | cargo2junit. It's implemented here.

[mathstuf]

Oh nifty. That's good to hear. I guess this can be closed then?

[svenstaro]

I just confirmed that the timings show up alright in GitLab so yeah. @johnterickson can you close this?

[mathstuf]

I can verify that this is working in my GitLab-based project as well.

[johnterickson]

Glad to hear this is all working!