Automation ID field does not work if test case names are different with test case names in automation project about trcli

[ddanielyan]

We are also experiencing the same issue, it seems the automation ID does not work if
Test Name on Test Rails and Test Name in the automation project do not match, was hoping to hear back if this is a bug or it is expected? Please update.

Thank you.

[molibdenmatt]

Hi,
Any updates on this?
I've got a similar case, even weirder one:

1. There are pretty complex BDD scenarios in my automation. One scenario is visible as a one in the Junit.xml report but this one scenario covers multiple TestCases in the TestRail
2. TestCases in TestRail are not changable. I can't edit their Titles
3. When I set the automation_id custom field to eg. xxx.yyy but the TC Title in TestRail is "zzz" the trcli parser uploads 0/0 results

I was hoping to add xxx.yyy automation_id to multiple TC's in TR and with one trcli run pass them all.

Could this be even configurable so the trcli shoud or should not care about the Test Title in TestRail? The automation_id is enough to map the TC's

[amuthan-sakthivel]

Hi Team, I am facing the same issue. It would make sense to have automation_id as the only thing to map the Test Cases

[d-rede]

Hello everyone!

Thanks for reporting this issue @tdnguyen84, it definitely wasn't an expected behavior. Version 1.3.1 was just released and should have this fixed by matching cases exclusively by automation_id. If this solves your problem, please close the issue :)