Quick import

Quick import copies a project from your current test management tool into Arcus, with folders, step groups, execution history, and custom fields.

Prerequisites

• Your tool’s credentials.
• The Jira integration for Jira Xray and Zephyr Scale, or Azure DevOps for Azure DevOps Test Plans.

Start a quick import

1. In the left navigation, go to Settings, then select Import.

2. Click Quick import from.

3. In Choose your current Test Management tool, select your tool: qTest, TestRail, Testmo, Jira Xray, BrowserStack, Zephyr Scale, Azure DevOps Test Plans, Qase, or TestMuAI.

The Quick import wizard opens on its first stage, Establish Connection.

Connect to your tool

qTest

1. In qTest Host name, enter your qTest site URL, for example https://yourcompany.qtestnet.com/.

2. In qTest API Key, enter your qTest API key.

3. If your project uses qTest Parameters, enter its URL in qTest Parameters URL, for example parameters.qtestnet.com.

TestRail

1. In TestRail Host name, enter your TestRail site, for example qa-team.testrail.io.

2. In TestRail Email, enter the email address you sign in to TestRail with.

3. In TestRail API Key, enter your TestRail API key.

Testmo

1. In Testmo Host name, enter your Testmo site, for example yourorg.testmo.net.

2. In Testmo API Key, enter your Testmo API key.

Jira Xray

Xray reads projects and users through your Jira connection, so connect Jira first. Once it is connected, a banner confirms it.

1. In Client ID, enter your Xray client ID.

2. In Client Secret, enter your Xray client secret.

BrowserStack

In API Token, enter your BrowserStack username and access key in the form username:access_key.

Zephyr Scale

Zephyr Scale reads project names and users through your Jira connection, so connect Jira first. Once it is connected, a banner confirms it.

1. In Zephyr Scale API Token, enter your Zephyr Scale API token.

2. In Region, select the region your Zephyr Scale instance runs in. It defaults to US.

Azure DevOps Test Plans

Azure DevOps Test Plans needs no credentials here. It uses your Azure DevOps integration instead. If Azure DevOps isn’t connected yet, Connect Azure DevOps says so: click Go to Integrations and connect Azure DevOps, then start the import again.

Qase

In API Token, enter your Qase API token.

TestMuAI

1. In Username, enter your TestMuAI username.

2. In Access Key, enter your TestMuAI access key.

Then click Test connection. Once Connection Tested Successfully appears, click Proceed.

Choose what to import

The How your <tool> data will be migrated to Arcus? panel shows what each item in your tool becomes in Arcus. Folder structure, execution history, and custom fields come across with them.

For qTest, for example:

qTest	Arcus
Test Cases	Test Cases
Test Releases	Test Plans
Test Cycles	Test Runs
Test Runs	Test Case Executions

Under Select Project, qTest has two options, both selected by default:

• Import all the test cycles and test releases brings cycles and releases as well as test cases.
• Include closed/completed items brings items already closed or completed in qTest.

1. Under Select Project, choose the options you want.

2. Select the project to import. The number of projects found appears beside Select Project.

3. Click Continue.

Map users

The Map Users stage lists every user in the source project. Each one needs an Arcus user, who becomes the owner of their items.

1. For each user, select an Arcus user under TMS USERS. Users mapped counts your progress.

2. Click Continue. It becomes available once every user is mapped. For tools without a Map Fields stage, this starts the import.

Map field values

qTest, Jira Xray, BrowserStack, Qase, and TestMuAI have a Map Fields stage. TestRail, Testmo, Zephyr Scale, and Azure DevOps Test Plans skip it and go straight to the import.

Map Fields pairs values from your tool with Arcus values. For qTest, the fields are Priority, Test case status, and Execution status. Values with the same name are matched automatically. Any other value is set to Create ‘<value>’, which adds it to Arcus as a new value.

1. Review each field. To use an existing Arcus value instead of creating one, select it from the list.

2. Click Begin Import.

Track the import

The last stage is named for what your tool imports: Import of Test Cases, Cycles & Releases for qTest, TestRail, Testmo, Zephyr Scale, and Azure DevOps Test Plans; Import of Test Cases, Plans & Executions for Jira Xray; Import of Test Cases, Plans & Runs for BrowserStack and Qase; and Import of Test Cases & Runs for TestMuAI.

The import queues, then starts when a worker is free. While it runs, counters show progress for each kind of item, such as test cases, folders, step groups, attachments, and comments. Click View details for more, or Cancel to stop.

Note

Don’t change the source project in your tool while the import runs. Changes made mid-import can make it fail.

When it finishes, Import completed shows how many items of each kind came across, and how many were skipped. Click Done to close the wizard, or Re-import to run it again.

Review the import results

Click Report on Import completed to open Import Results. It has a tab for each kind of item, such as test cases, test releases, and test cycles. Each tab shows:

• Totals for imported, skipped, and failed items.
• Failed to import: each item’s ID, title, error type, and the reason it failed.
• The imported items, with their new Arcus ID and folder.

Click Report on this page to download the results.