Closed arielelkin closed 10 months ago
Hello @Testinator-X , thanks for your response.
Nope I haven't set up that custom field. In any case, this is a bug in trcli
as I'd expect it to output an error message to that effect, rather than crash as it currently does.
By the way, the installation instructions don't mention that setting up the automation_id
custom field is necessary for trcli to run, so consider modifying the docs accordingly.
I set the automation_id. The first one succeeded in uploading, but the above error occurred from the second one. T_T
Hello @arielelkin
I'm glad you were able to ultimately figure it out.
Setting up the automation_id
is not a requirement to use the CLI itself. It is a requirement for the Code-first workflow, where we explain how to set up the field.
We do have a check in place in the CLI code to warn users if they haven't configured the field, unfortunately we can't detect all situations where it may be misconfigured so, in very particular occasions, this error may occur.
Since this is no longer an active blocker, I'm closing this issue and we will follow-up on https://github.com/gurock/trcli/issues/144.
TestRail CLI Version
1.5.0
CLI Environment
macOS 13.4.1
TestRail Version
TestRail v8.0.1 Default (1030)
TestRail Instance Type
Professional Cloud
Current behavior
Here's a sample report file: junit-report.xml.zip
Desired behavior
No response
More Details
No response