Forum Discussion
Hi schef, joseph_michaud and Colin_McCrae,
Found the source of the problem thanks to schef's last reply and it has nothing to do with schef's scripts.
TestRail address was incorrect although that wasn't the only problem. Also TestRail has an awkward way to reference test cases in a test run. Using the method add_result_for_case passing runId and caseId it's a bit tricky as the caseId in this case is the test case number (C) not the Test (T) from the test run.
Yes as complicated as it sounds that's the source of the problem. So basically TestRail references a test case in a run using RunId + CaseId instead of RunId + TestId (which is generated for each test run).
Thank you all for the good effort and support as it would have been impossible to get it working without you. Much appreciated.
Cheers,
Leo
- Colin_McCrae8 years agoCommunity Hero
"So basically TestRail references a test case in a run using RunId + CaseId instead of RunId + TestId (which is generated for each test run)."
That's what I was alluding to in my "**BRAINWAVE**" post further up. TFS is much the same. A test case always carries it's own ID, which is permanent, but when part of a test run, it carries a Run ID for that run only. Same idea with TestRail. And it makes sense when you stop and think about it. But does make referencing things a little more awkward.
Glad you got it sorted out. :)
Related Content
- 3 years ago
- 12 years ago
Recent Discussions
- 5 days ago
- 5 days ago