What would you like the TestRail CLI to be able to do?
I don't see possibility to map junit xml result to desired or custom statuses for testcases and steps.
Why is this feature necessary on the TestRail CLI?
Current mapping is not correct. Broken test has error tag in junit xml, which is mapped to Failed (same as failed with assertion, with failure tag)
However for such broken test more suitable retest status. For skipped tests more suitable untested or blocked instead of retest, since usually such tests are skipped by reason.
Same problem with steps. Skipped step is more related to untested. And not all mappings are present. For instance I would like to have possibility mark step as retest or with any other system or custom status.
More details
Currently I see only these statuses for step are available:
status_dict = {
"passed": 1,
"untested": 3,
"skipped": 4,
"failed": 5
}
Testinator-X
commented
3 weeks ago
What would you like the TestRail CLI to be able to do?
I don't see possibility to map junit xml result to desired or custom statuses for testcases and steps.
Why is this feature necessary on the TestRail CLI?
Current mapping is not correct. Broken test has error tag in junit xml, which is mapped to Failed (same as failed with assertion, with failure tag) However for such broken test more suitable retest status. For skipped tests more suitable untested or blocked instead of retest, since usually such tests are skipped by reason. Same problem with steps. Skipped step is more related to untested. And not all mappings are present. For instance I would like to have possibility mark step as retest or with any other system or custom status.
More details
Currently I see only these statuses for step are available: status_dict = { "passed": 1, "untested": 3, "skipped": 4, "failed": 5 }
Interested in implementing it yourself?
No