Version 1.6

[d-rede]

Issues

• Enhancements
  • https://github.com/gurock/trcli/issues/129
  • https://github.com/gurock/trcli/issues/136
  • https://github.com/gurock/trcli/issues/85
  • https://github.com/gurock/trcli/issues/146
  • https://github.com/gurock/trcli/issues/74
• Bugs
  • https://github.com/gurock/trcli/issues/137
  • https://github.com/gurock/trcli/issues/110

Solution description

How are we solving the problem?

• Multiple enhancements and bug fixes

Changes

What changes where made?

• Robot Framework report parser using command parse_robot
• Add test runs to test plan using --plan-id (with configurations support using --config-ids)
• New JUnit property for result steps testrail_result_step
• Test run update allows adding new tests
• Added --suite-name parameter
• Fixed suite lookup by name method

PR Tasks

• [x] PR reference added to issue
• [x] README updated
• [x] Unit tests added/updated

[lscottnaim]

@d-rede I'm confused by the conclusion of #138. I thought I would be able to simply give a plan ID and if a test case was found in a run inside a plan, it would drill down to check and update it.

i.e.

trcli -n -c /home/liam/git/config.yaml parse_junit --title "NAME-OF-TITLE" --case-matcher "name" --plan-id 3246 --suite-id 1671 --result-fields version:3.8.4.5453.0 --allow-ms -f /home/liam/git/reports/test-report.xml

[d-rede]

Hello @lscottnaim

I looked at the title of the issue and wrongly assumed it was this implementation we've been meaning to do for a while. My apologies, I should have taken a closer look at the description of the feature you requested.

Having said that, I will re-open the issue, but I can make no promises as to whether it is a behavior we want to implement or not at this point.