Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect statuses mapping #237

Open
unroma opened this issue Jun 12, 2024 · 1 comment
Open

Incorrect statuses mapping #237

unroma opened this issue Jun 12, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@unroma
Copy link

unroma commented Jun 12, 2024

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

@unroma unroma added the enhancement New feature or request label Jun 12, 2024
@Testinator-X
Copy link
Contributor

Duplicates #107

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants