Automation test runs - test duration is always 00:00:00 for nunit results files

When using the CLI importer and nunit.xml report files, the duration of tests are always 0 in Testiny.

The duration does appear to be correctly within the file:

At the top level:

<test-run id="2" testcasecount="2" result="Passed" start-time="2025-11-03 08:51:36.419827" end-time="2025-11-03 08:52:17.091124" duration="40" total="2" passed="1" failed="1" inconclusive="0" skipped="0" asserts="0" clr-version="3.13.7 (tags/v3.13.7:bcee1c3, Aug 14 2025, 14:15:11) [MSC v.1944 64 bit (AMD64)]" engine-version="3.6.2">

Each test suite:

<test-suite id="xxxx" name="xxx" fullname="xxx" methodname="" classname="" runstate="Runnable" type="Assembly" testcasecount="2" result="Passed" label="" start-time="2025-11-03 08:51:37.120097" end-time="2025-11-03 08:52:17.089129" duration="39.969032" asserts="0" total="2" passed="1" failed="1" warnings="0" inconclusive="0" skipped="0">

And per test:

<test-case id="100" name="xxxx" fullname="xxxx" methodname="xxxx" classname="xxxx" runstate="Runnable" seed="1" result="Failed" label="" start-time="2025-11-03 08:51:37.120097" end-time="2025-11-03 08:52:12.384395" duration="35.264298" asserts="0">

Example screenshot (for a different result than above):

image

junit.xml files are ok, which we sometimes use as an alternative.

Hello David,
Thanks for reporting this.
It seems that newer v3 format files use “duration” vs. “time” in v2 (and old v3 files) – we will correctly support this in one of the upcoming releases.

Regards,
Michael