These FAQs will help you navigate the CSV import and export functionalities in Qase efficiently.
If you have more questions or encounter any issues, feel free to reach out to our support team for assistance.
Can I change the casing or modify headers of the CSV?
No, when working with the CSV file, do not modify the headers or change the casing. Please keep the headers untouched to ensure successful mapping upon import.
Do I need to fill in all fields when creating a test case in a CSV file?
No, if you're creating a test case in the CSV, only the title is mandatory. Other fields can be left empty if not relevant to your initial setup.
In the CSV, how do I nest a new test case under a suite?
To add a new test case to a suite in your CSV file, start by providing the suite's name and ID at the beginning.
Give the suite a name and ID and fill the
suite_without_casescell with a value of 1, to indicate it as a suite.Then, in the test case row, mention the ID and name of the suite where you want to nest the test case.
Can I modify test cases after bulk editing them using spreadsheet software?
You can easily modify test cases' properties in bulk by using Qase's built-in edit option. It's much easier compared to editing them using a spreadsheet.
You can easily modify test cases' properties in bulk by using Qase's built-in edit option. It's much easier compared to editing them using a spreadsheet.
If you prefer using a spreadsheet for bulk editing -
Export the test cases you want to modify, in a CSV format.
Modify the data using your spreadsheet software.
When importing, select 'Replace test cases on match' to update the test cases with your modifications.
To ensure accurate matching with your repository, please refrain from modifying the case IDs in the CSV.
Can I carry over attachments, custom fields from my current TMS?
The import options in the UI does not migrate attachments, and custom field data.
Please, get in touch with us at [email protected] for migration and onboarding options If you're migrating from TestRail.
What if my TMS is not listed in the Source type while importing?
If your current TMS is not listed as a Source type, you can follow these steps -
Download the Sample CSV, which has prescribed formatting, from here.
Export your data from your current TMS and paste all the relevant data into the Sample CSV file.
Import the CSV file by choosing Qase.io as the Source type.
If the Sample CSV lacks a field [column] for transferring data from your current TMS export file:
Create a custom field in your Qase workspace. [ ⚠️ Available in paid plans only ]
Export your repository to a CSV file. It will now have a column for your custom field to the far right.
Continue with steps 2-3 from before.
I see this error message: "0 cases modified, 0 suites, and 0 cases were successfully imported!"
If you encounter this message, double-check your CSV file to ensure no headers are modified.
How do I create test case steps inside the CSV file?
You can create both classic and gherkin steps inside the CSV file. Ensure to define the steps_type column accordingly.
Refer to this image to understand the numeration of steps.
Refer to this image to understand the numeration of steps.
I don't see my test case steps in the export
If you've exported your data to XLS format and can't find the test case steps, check the other sheet in the document. Test case steps are placed on a different sheet.
For a more convenient export that includes test case steps on the same sheet, consider using the CSV format.