TRCLI-135: Added support for multiple case ids in single test execution for parse junit#390
Open
acuanico-tr-galt wants to merge 2 commits intorelease/1.13.1from
Open
TRCLI-135: Added support for multiple case ids in single test execution for parse junit#390acuanico-tr-galt wants to merge 2 commits intorelease/1.13.1from
acuanico-tr-galt wants to merge 2 commits intorelease/1.13.1from
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue being resolved: #130 #343
Solution description
Implemented support for mapping multiple TestRail case IDs to a single JUnit test execution. When a testwith multiple case IDs executes, all mapped cases receive the same result status, elapsed time, comments, and attachments. This allows teams to combine multiple test scenarios into one automation test while still having the option to update all corresponding TestRail cases.
Changes
Potential impacts
None. The changes are backwards-compatible.
Steps to test
Property-based (comma-separated):
XML:
trcli parse_junit -f test.xml --case-matcher property
Name-based (bracket format):
XML:
trcli parse_junit -f test.xml --case-matcher name
PR Tasks