Set automation_id case field when using --case-matcher: "property"

[ryangilbert]

What would you like the TestRail CLI to be able to do?

I'm working with codebase that is partially documented in Testrail, so using the specification-first approach, with --case-matcher: "property".

For issues that do not have an existing case id, I want to the new test cases that are added to have their automation_id added automatically. This is working when I use --case-matcher: auto, but does not work if I switch to --case-matcher: "property". This would save us a lot of manual updating and safeguard against duplicate test cases being added.

Is there any workaround for this?

Why is this feature necessary on the TestRail CLI?

To prevent duplicate test cases from being added, while saving a lot of manual work.

More details

No response

Interested in implementing it yourself?

No

[bitcoder]

Hey @ryangilbert ,
that's a great question.
Right now,

• if you use --case-matcher: "property", the flow assumes that someone wants to report against existing test cases.. so the idea is that you're automating something that already exists; it's the so called specification-first approach
• if you use --case-matcher: "auto", the flow assumes that someone wants to report automation results... and that automation is somehow the driver.. it's the so called code-first approach

There's currently no support for an hybrid-like approach where you could report results for existing test cases (by id on a property or on the test name) and autoprovision the other test cases that don't have any reference to an existing test case..

The following paragraph is not very clear to me:

For issues that do not have an existing case id, I want to the new test cases that are added to have their automation_id added automatically. This is working when I use --case-matcher: auto, but does not work if I switch to --case-matcher: "property". This would save us a lot of manual updating and safeguard against duplicate test cases being added.

1. when you use --case-matcher: "property", no new test cases are created correct? Because you say "test cases that are added..." . Or are you using --case-matcher: "property", together with -y ?
2. what is exactly the scenario where you get duplicate test cases? can you detail a concrete example please, with same content? I have an idea but I want to double check if you're thinking about the same scenario as I am