Closed SonnyGe closed 2 years ago
@billylam please check
Please hold. I'm busy personally and professional and this may take a while to get to, but also it's been less than 24 hours.
If you need this sooner consider npm linking within your repo, or publishing your own npm fork.
Current implementation of "strictCaseMatching" support handling only one type of error - "if a test case found is not apart of the suite". But in practice, sometimes we have situations when we need to export to already created test run our test results, which includes cases not part of the test run . And instead of just skipping such results testrailApi show error like:
This PR solves this problem by adding a new testRail request (/api/v2/get_tests/runId).