If the test cases you’re bringing into Qase already have some kind of structured hierarchy, like a parent-child folder setup, you can reflect that structure using nested suites. This lets you create parent and child suite relationships so related tests stay grouped in a way you want.
In this section, we’ll show you how to use the fourth suite column, suite_parent_id.
To get some hands on practice, we’ll start by exporting your existing repository again. Here’s a reference file you can use if you want to follow along.
This time, we’ll move the suites “Launch Control” and “Navigation Control” under a new common parent suite called “Core Workflows.”
As before, suites go at the top of your CSV, right after the headers. Let’s add a new row for our latest parent suite “Core Workflows”.
We'll define it like any other suite and assign it a suite_id of 8. To determine what ID to assign, check how your existing suites are numbered and pick the next number in the sequence, in this case, 8.
Finally, set the suite_without_cases column to 1 to indicate that this row represents a suite, not a test case.
Next, for the suites we want to make child suites, simply add the ID of “Core Workflows” in their suite_parent_id column. This will indicate that these suites should be nested under the parent suite.
The same applies to the test cases inside these child suites, add the ID of “Core Workflows” in their suite_parent_id column so they follow the hierarchy.
That’s it! Upload the CSV, and your repository will now show the parent child hierarchy.
How to Handle Multiple Levels of Nested Suites?
If you have three or more levels of nested suites, let's see how to configure that.
Let’s say you want to add a new parent above “Core Workflows” called “UI Tests.” In this scenario, the “UI Tests” suite gets assigned an ID of 9.
Since “Core Workflows” should now sit under the new parent “UI Tests,” its suite_parent_id should be set to 9, linking it to that parent.
The existing mapping between “Core Workflows” and its child suites doesn’t change.
For example, “Launch Control” and “Navigation Control” can still have their suite_parent_id set to 8, which is the ID of their immediate parent suite, “Core Workflows.”
The same logic applies to the test cases inside these child suites. Their suite_parent_id should match the ID of the immediate parent suite of the suite they belong to.
So, a test case under “Launch Control” will still have the suite_parent_id set to 8, since “Launch Control”’s parent is “Core Workflows,” which has the ID 8.
