If your test cases are already organised into folders or groups in your old tool, you’ll definitely want to keep that structure when you move to Qase.
This can be done using suites, they’re attributes of your test cases that help keep the cases organised in the repository.
The question is: how can suites be added using CSV imports?
When working with suites, we’ll focus on just four columns.
Your CSV will still have the header row, which stays as is.
Suites live at the very top of your CSV file as their own rows. For each suite, add a new row with the suite ID (in the suite_id column) and the suite name (in the suite column). Unlike test case IDs, you can specify the suite ID. Start with 1 for your first suite, then increment for each additional suite (2, 3, 4…).
Now, how does Qase know whether a row is for a suite or a test case? That’s where the suite_without_cases column comes in. Set it to 1 to indicate that this entry is a suite, not a test case
Once your suites are in place and you have their IDs, you can map your test cases to them. Each test case just needs to point to the specific suite_id and suite name where it should belong.
Upload this file, and if you’re reassigning existing test cases to the newly created suites, make sure to keep the “Replace matching test cases” box checked.
The suites, once uploaded will appear like this -
Why suites should be defined before test cases?
You probably noticed that each test case needs a suite ID to be assigned to a suite.
Without that ID, a test case doesn’t know where it belongs and will end up under the “Test cases without Suites” section.
That’s why it makes sense to create your suites first. Once the suites are in place, you’ll have the suite IDs ready, and you can use them to map your test cases.
Take care of the structure first, then upload your cases, and your repository will grow in an organized way.
At the start of this section, we mentioned that working with suites involves four columns. So far, we’ve focused on just three. Next, we’ll dive into the fourth column, “suite_parent_id”, and see how it’s used to create parent child relationships between suites.