Batch imports come in handy when you have a large number of test cases and don’t want to upload everything at once. Breaking your data into smaller chunks can make the process faster and, if something goes wrong, much easier to troubleshoot since you’re working with fewer cases at a time.
Before we dive into the import process, we’ll start by exporting the current repository. If you already have some test cases uploaded, this gives us a ready made CSV to work from. The idea here is simple: you don’t have to start from scratch. By exporting your existing repo, you get the exact upload template you need, and you can build on it.
Open the exported file, and you’ll see all your existing test cases along with their case IDs. Leave those IDs exactly as they are, don’t change, remove, or edit them.
To add new test cases, scroll to the bottom of your CSV and start adding new rows. For these new entries, leave the id field blank. At this stage, you can only fill in the title.
Once that’s done, your file is ready to be uploaded.
While uploading, there’s one important step.
⚠️ Make sure to check the “Replace matching test cases” checkbox.
And hit on "Import test cases". The new cases should be added to the repository, while the existing tests remain as is.
Let’s break down what’s happening here. When the “Replace matching test cases” checkbox is checked, Qase uses the id field to decide what to do with each row in your CSV.
If the id is empty, it treats the row as a brand new test case and creates it. If there’s an id present, Qase finds the matching test case in your repository and updates it with any changes you’ve made.
If you don’t check that box, Qase treats every row in your import as a new test case, even the ones that already have IDs. That means you’ll end up with duplicates of your existing cases.
With the box checked, Qase matches the IDs and updates existing cases instead, so this problem doesn’t happen.
Now that your repository is starting to grow, you’ll probably want to get everything organized, especially if you’re coming from a tool where your tests were already structured a certain way. We’ll dive into that in the next section.