Robot Framework test suites creation does not take into account suites hierarchy

[pf-loic]

I have the following test suite hierachy in my PF project:
Tests
=>Account
=> Login

So I was expecting the reporter to create a similar hierarchy in Qase, but it only creates a suite with the last leaf folder (Login). Move over, if it decide to move this folder into another parent manually in Qase, then the test case are recreated on the next run of the reporter (because i'm not using the Qase ID tags on RF tests on my project, and i would try to avoid to).

Find below an analysis of the code base made by Claude Sonnet 4.6. I have litterally no idea if this is relevant or now, but it's free to share ^^.

Bug: Robot Framework listener does not preserve test suite hierarchy

Package: qase-robotframework
File: qase/robotframework/listener.py

Description:

When running Robot Framework tests with nested suites (e.g. Tests > Account > Login), the Qase listener only creates a single flat suite (e.g. Login) instead of the full hierarchy.

Root cause:

__extract_tests_with_suites() correctly builds the full hierarchy as a flat list (e.g. ["Tests", "Account", "Login"]), but in end_test, each suite name is added to the Relation object as a separate, independent SuiteData entry:

This results in Qase receiving multiple flat suite entries rather than a nested hierarchy. Based on how the Qase API processes these entries, only the last (or deepest) suite name ends up being used, discarding all parent levels.

Expected behavior:

A test in Tests > Account > Login should appear under the full nested suite path Tests / Account / Login in the Qase UI.

Actual behavior:

The test appears under a single suite named Login with no parent hierarchy.

Environment:

Robot Framework 7.x
qase-robotframework (latest)
qase-commons (latest)

[gibiw]

Fixed in qase-robotframework 6.0.0 via #488.

The listener now preserves the full suite hierarchy from the run root down to the leaf, so a test in Tests > Account > Login will land in the corresponding nested suite tree in Qase instead of a flat Login suite.

This is a breaking change for projects whose Qase suites were created under the old flattened layout — see the upgrade guide for migration steps. Thanks for the report and the detailed analysis!