parse_robot report errors

[hansqc]

I checked my Robot Framework test result, it looks normal, same structure as in the sample.
Following is the output from trcli:

TestRail CLI v1.9.8
Copyright 2024 Gurock Software GmbH - www.gurock.com
Parser Results Execution Parameters

Report file: output.xml
Config file: None
TestRail instance: https://xxx.testrail.io (user: )
Project: MMPro Frontend Automation
Run title: Robot Framework intergration test
Update run: No
Add to milestone: No
Auto-create entities: True
Parsing Robot Framework report.
Processed 60 test cases in 1 sections.
Checking project. Done.
Found 59 test cases without case ID in the report file.
Nonexistent case IDs found in the report file: [127]
Error occurred while checking for 'missing test cases': 'Case IDs not in TestRail project or suite were detected in the report file.'
Adding missing sections to the suite.
Removing unnecessary empty sections that may have been created earlier. Removed 1 unused/empty section(s).
Creating test run.
Field :case_ids contains unrecognized case IDs.
Unable to delete created section: Field :section_id is not a valid section.

[acuanico-tr-galt]

Hi, @hansqc based on the error this might be caused by the following:

1. 59 test cases without case ID = This means only 1 test case had a case ID, and TR CLI is trying to match the others using names
2. Nonexistent case IDs found in the report file = The case ID 127 exists in your XML but does not exist in your TestRail project. If you’re using multiple suites, this might refer to a case ID in the wrong suite, Case IDs must belong to the exact suite or project referenced in your TR CLI command.
3. Field :case_ids contains unrecognized case IDs = This often happens when you pass case IDs that aren’t resolved properly, usually from: Malformed XML, Incorrect Case ID format, TestRail project/suite mismatch.
4. Unable to delete created section: Field :section_id is not a valid section = It tried to delete an auto-created section but failed maybe due to previous errors.

Suggestions:

1. Fix Your Robot Framework Test Names - Ensure all test names include case IDs and these exists in TestRail
2. Add Missing Test Cases Automatically using the -y option
3. Verify Case ID (e.g. 127) - Check whether case ID 127 exists in the exact project and suite you’re targeting. If using suite mode, you may need to explicitly specify suite ID in the CLI.
4. Add -v for verbose logging when executing the command. This is helpful to identify exact payloads being sent to TestRail and what’s failing.

Thank you.