Import from CSV
Import via CSV adds test cases to the current project in bulk, from your own spreadsheet or from another tool’s export.
Prerequisites
Get a CSV file
Section titled “Get a CSV file”Any .csv file with one test case per row works. Arcus maps its columns to test case fields during the import, so the column names don’t need to match.
-
In TestRail, go to Projects > Test Cases.
-
Select the test cases, click the Export icon, and select Export to CSV.
-
In Export to CSV, select the Sections (folders) and Columns (properties and values) to export.
TestRail downloads the test cases as a .csv file.
-
In Jira, go to Projects, then select the Zephyr tab.
-
Select the folder that holds the test cases.
-
Select the test cases, click More, and select Export to Excel.
-
Convert the downloaded
.xlsxfile to.csv.
-
In BrowserStack Test Management, go to Projects > Test Cases, then select the folder that holds the test cases.
-
Select the test cases, click Export, and select Export as CSV.
BrowserStack downloads the test cases as a .csv file.
To copy a whole project with its runs and history instead, use Quick import, which connects to TestRail, Zephyr Scale, BrowserStack, and 6 other tools directly.
Upload the file
Section titled “Upload the file”-
Open the project switcher at the top of the left navigation, click Project Settings, then open Import.

-
Click Import via CSV, then choose the template that matches your test cases:
- Steps for test cases written as steps.
- Document for test cases written as a single description.

-
Click Upload File and select the
.csvfile. Uploaded File Preview opens.
-
Check the file content, then click Next.
You can also open the Import page from the Dashboard, under Import Test Cases (.csv), by clicking Import, or from Test Cases, by clicking the more options icon (⋯) at the top of the page and then Import.
Map columns to Arcus fields
Section titled “Map columns to Arcus fields”Map Properties and Values has two panels: Map Properties, where each CSV column is matched to an Arcus field, and Test Case Preview, which shows a test case as it will be imported. Arcus maps the columns automatically.
-
Review the mapped fields. Change any column that is missing or mapped to the wrong field.
-
Check the result in Test Case Preview.
-
Click Begin Import.
Arcus creates an import log on the Import page to track progress and results.
Review the import results
Section titled “Review the import results”When the import finishes, open its log from the Import page. Import Results shows:
- Totals for all, imported, skipped, and failed test cases.
- Failed to import: each test case’s error type and the reason it failed, for example a duplicate title.
- Skipped test cases, for example ones that already exist in the project.
- The imported test cases, with their details.
To bring in the failed test cases, fix them in your .csv file and import it again.
Import step groups
Section titled “Import step groups”Step groups import from the Step Groups tab of the same Import page. There’s no template to choose.
Lay the file out with one step group per block of rows. A row with a title starts a new step group, and the rows below it, up to the next title, are its steps.
Title,Description,Step,Expected resultLog in as admin,Signs in with the admin account,Open the sign-in page,The sign-in form shows,,Enter the admin email and password,,,Click Sign in,The dashboard opensSearch for a stay,,Enter a city in the search box,,,Click Search,Results show for that cityThe mapping screen has four step group fields: Title and Step Description, which are required, and Description and Step Expected Results. Arcus gives each step group its ID.
-
Open the project switcher at the top of the left navigation and click Project Settings.
-
Open Import.
-
Open the Step Groups tab.
-
Click Import via CSV.
-
Click Upload File and select the
.csvfile. Check the file content, then click Next. -
Under Map Properties, check the mapped fields and change any that are missing or wrong. Step Group Preview shows a step group as it will be imported.
-
Click Begin Import. Arcus shows “Data Import Started” and returns to the Import page.
A step group whose title already exists in the project is skipped, and so is a second step group with the same title in the file. Titles are matched without regard to case. Open the import’s log on the Step Groups tab to see the totals for Imported Step Groups, Skipped Step Groups, and Failed Step Groups. Skipped lists each skipped step group’s TITLE and REASON, such as “Step group with title ’…’ already exists in this project”.
Was this page helpful?
Thanks for the feedback.