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
What would you like the TestRail CLI to be able to do?
I'd like to be able to create a run using the add_run command recently added by #236 and then use a similar command to close the run with similar syntax, with the option to use the yaml file produced by add_run.
Why is this feature necessary on the TestRail CLI?
I'm using parse_junit in my CI pipeline to upload multiple JUnit reports and preceding this automation with an add_run command to create a run for all of them to use. At the moment my automation has fairly brittle logic that loops through a list of reports and when it detects the last report, runs parse_junit with the --close-run flag to close the run. The problem with this approach is that if the parse_junit command fails for any reason, the run is left open, which is not ideal for our internal process.
More details
Here's the type of logic I'd like to support:
trcli add_run...
loop through list of junit reports and trcli parse_junit using a config.yml produced by add_run
handle errors
trcli close_run...
Interested in implementing it yourself?
Yes
The text was updated successfully, but these errors were encountered:
What would you like the TestRail CLI to be able to do?
I'd like to be able to create a run using the add_run command recently added by #236 and then use a similar command to close the run with similar syntax, with the option to use the yaml file produced by add_run.
Why is this feature necessary on the TestRail CLI?
I'm using parse_junit in my CI pipeline to upload multiple JUnit reports and preceding this automation with an add_run command to create a run for all of them to use. At the moment my automation has fairly brittle logic that loops through a list of reports and when it detects the last report, runs parse_junit with the --close-run flag to close the run. The problem with this approach is that if the parse_junit command fails for any reason, the run is left open, which is not ideal for our internal process.
More details
Here's the type of logic I'd like to support:
Interested in implementing it yourself?
Yes
The text was updated successfully, but these errors were encountered: