[CLI] Pytest - Show problem cases names in error message during upload failure

[lscottnaim]

Problem to solve (from the user’s perspective)

When a large multiparser job fails due to case IDs missing, the user then needs to check all their JUNIT xml's (or one large one) for the specific case that is causing the upload to fail.

TestRail CLI v1.15.1
Copyright 2025 Gurock Software GmbH - www.gurock.com
Parser Results Execution Parameters
> Report file: ~/git/reports/*-report.xml
> Config file: XXX
> TestRail instance: XXX
> Project: XXX
> Run title: XXX
> Update run: No
> Add to milestone: No
> Auto-assign failures: No
> Auto-create entities: False
Parsing JUnit report.
Processed 5 test cases in section pytest.
Processed 14 test cases in section pytest.
Processed 7 test cases in section pytest.
Processed 4 test cases in section pytest.
Processed 5 test cases in section pytest.
Processed 6 test cases in section pytest.
Processed 1 test cases in section pytest.
Processed 1 test cases in section pytest.
Processed 2 test cases in section pytest.
Processed 4 test cases in section pytest.
Processed 14 test cases in section pytest.
Processed 5 test cases in section pytest.
Processed 1 test cases in section pytest.
Processed 5 test cases in section pytest.
Processed 2 test cases in section pytest.
Processed 37 test cases in section pytest.
Processed 2 test cases in section pytest.
Processed 1 test cases in section pytest.
Processed 9 test cases in section pytest.
Processed 3 test cases in section pytest.
Processed 2 test cases in section pytest.
Processed 3 test cases in section pytest.
Processed 4 test cases in section pytest.
Processed 5 test cases in section pytest.
Processed 6 test cases in section pytest.
Processed 17 test cases in section pytest.
Processed 6 test cases in section pytest.
Processed 5 test cases in section pytest.
Processed 2 test cases in section pytest.
Processed 9 test cases in section pytest.
Processed 2 test cases in section pytest.
Processed 25 test cases in section pytest.
Processed 34 test cases in section pytest.
Processed 5 test cases in section pytest.
Processed 4 test cases in section pytest.
Processed 5 test cases in section pytest.
Processed 46 test cases in section pytest.
Processed 1 test cases in section pytest.
Processed 6 test cases in section pytest.
Processed 7 test cases in section pytest.
Processed 6 test cases in section pytest.
Processed 3 test cases in section pytest.
Processed 5 test cases in section pytest.
Processed 8 test cases in section pytest.
Processed 1 test cases in section pytest.
Processed 2 test cases in section pytest.
Processed 4 test cases in section pytest.
Multisuite mode: Preparing cross-suite test plan...
Checking project. Done.
ERROR: All test cases must have case IDs when using multisuite parser. Found 1 case(s) without IDs.
2026-07-22 11:03:52,737 ERROR Command exited with code 1

How could we improve this?

Print the name of the cases that having missing IDs in the error message

Checking project. Done.
ERROR: All test cases must have case IDs when using multisuite parser. Found 2 case(s) without IDs.
Cases to check: test_example_thing, test_another_thing
2026-07-22 11:03:52,737 ERROR Command exited with code 1

Primary value dimension

Productivity — less time to achieve the task

If you selected “Other”, describe the value dimension

No response

Where is the limitation?

CLI — behaviour/UX/flags issue

CLI version (fill if CLI is involved)

trcli 1.15.1

TestRail version/edition (fill if API is involved)

No response

What improves, and by how much?

The user is able to easily find the tests that cause the failure to upload

KPI(s)

Time to finds tests without valid IDs

Urgency

Low — incremental improvement

Proposal (CLI-level sketch)

A simple addition to the error message