You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We run a somewhat involved nightly test set up and use want to use gotestsum to generate coverage reports. We've been running into an issue where the execution time of the test is not included in the report. We run something similar to this:
Thank you for raising this issue! Currently the time is based on runtime of the gotestsum command.
We could add a flag to use the timestamps in the json instead of wall clock time for cases like this. I think that would be a great addition.
As a workaround you could use run the tests with gotestsum --junitfile report.xml --jsonfile test.json possibly with --raw-command if you have a complicated command to run. That way you'll get the correct runtime and still get the JSON output to a file.
Hi,
We run a somewhat involved nightly test set up and use want to use gotestsum to generate coverage reports. We've been running into an issue where the execution time of the test is not included in the report. We run something similar to this:
test.json
includes the execution time of the tests.The text was updated successfully, but these errors were encountered: