Automation test runs - test "Started At" isn't correct for junit results files

When using the CLI importer and junit.xml report files, the “Started At” time is older than it should be.

After some investigation, it seems that it is not taking the timestamp field from the results file, but instead it is taking the “Date created” time from the file itself.

This is a problem for pytest, as it does not create a new file when producing results, it overwrites the existing file. Therefore the date created is much older than the test run start time.

Note that nunit.xml files do not have this issue, despite the behaviour being the same in pytest. The file creation date is the same as with junit, but Testiny displays the correct test start time, matching the start-timeinside the report.

Hello David,
The timestamp is currently not correctly applied for files using a <testsuites><testsuite>.. structure.
We will add proper support for per-suite timestamps in one of the upcoming releases.

Regards,
Michael