testomatio
Bug - Uploading an automated test run uses the upload time as the execution start/finish rather than the actual start/finish time from the run
Describe the bug A test in Robot Framework is run, with the -x option to produce xml output in JUnit format. The xml is uploaded to testomat using framework/language as other/other. The xml uploads successfully, and correctly captures that test name, step names, pass/fail status, and time to complete. However, in Testomat the "Executed Time" ends up being set to the time the upload occurred, rather than the time the test was actually executed.
To Reproduce Steps to reproduce the behavior: See above description
Expected behavior The actual date/time the run happened is what is in the test executed field in Testomat
Screenshots
Desktop (please complete the following information):
- Win 11
- CLI for uploading
- Production
Additional context Add any other context about the problem here.
@AZANIR please check this on your side.
Verified — JUnit XML import reproduces the same issue
We’ve tested the scenario described by @vhladik and successfully reproduced it using a JUnit XML report uploaded via @testomatio/reporter.
Environment:
OS: Windows 11
Node.js: v22.20.0
@testomatio/reporter: v2.3.6
Testomat instance: beta.testomat.io
Upload command:
TESTOMATIO_URL=https://beta.testomat.io
TESTOMATIO=tstmt_***
npx @testomatio/reporter report --xml "reports/junit-results.xml" --lang "other"
JUnit XML sample:
Expected result:
Executed time in Testomat should match the timestamp from the
Actual result: Executed time is set to the upload moment (e.g. Oct 27, 2025 11:49), ignoring the XML timestamp value.
✅ The issue is reproducible with JUnit XML import — reporter currently does not map
