TRCLI-162: Multisuite parser to process multiple suites in a single test plan#406
TRCLI-162: Multisuite parser to process multiple suites in a single test plan#406acuanico-tr-galt merged 10 commits intorelease/1.14.0from
Conversation
…nd updated readme guide
…ed data, also resolved mutated data structure issue in handling test sections accross iterations
|
Hello! This will fix my issue if it gets released. Very exciting! One question, let's say I have multiple suites and over 300 test cases in total. If one of my IDs is incorrect for whatever reason, will this break uploading the results to the valid cases? |
…o be handled internally by add_result
|
Hi @lscottnaim No, a single invalid case ID will not break the entire upload. The invalid case id will only be skipped and the valid ones will still be uploaded. Moreover, The parser only exits with error if ALL cases are invalid or ALL valid cases belongs to a different project. Thank you for your constant support! |
|
@acuanico-tr-galt I've just had an opportunity to try this, and it seems my fears were correct. If I upload all my cases with some inaccuracies it just fails to upload: EDIT: Looks like I had a case like `test_caseName_C1234_example. That breaks the upload. |
Issue being resolved: #348
Solution description
If the test automation spans multiple TestRail suites, the multisuite parser (--special-parser multisuite) allows you to create a single test plan with one run per suite from a single JUnit XML report. The CLI automatically detects which suite each test case belongs to, groups them accordingly, and creates or updates a test plan with the appropriate structure.
test_idproperties)--case-matcher nameor--case-matcher property(notauto)Changes
Potential impacts
None. Changes are all backwards compatible.
Steps to test
Happy path to test implemented scenario
PR Tasks