Skip to content
Docs
Arcus
Popular questions
↑↓ to navigate↵ to selectesc to close
Book a demo

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 (recommended for Zephyr Scale), or Azure DevOps for Azure DevOps Test Plans.
  1. Open the project switcher at the top of the left navigation, click Project Settings, then open Import.

    Project Settings > Import. Callouts mark (1) Import, and (2) Import via CSV and (3) Quick import from.

  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.

    Choose your current Test Management tool, listing qTest, TestRail, Testmo, Jira Xray, BrowserStack, Zephyr Scale, Azure DevOps Test Plans, Qase, and TestMuAI.

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

  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.

For every tool except Azure DevOps Test Plans, click Test connection. Once Connection Tested Successfully appears, click Proceed.

The Establish Connection stage for qTest. Callouts mark (1) the import stages, (2) Test connection, and (3) Proceed.

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.

Under Select Project, each tool has two options, both selected by default. The first brings plans, runs, or cycles as well as test cases. Include closed/completed items brings items already closed or completed in your tool.

qTestArcus
Test CasesTest Cases
Test ReleasesTest Plans
Test CyclesTest Runs
Test RunsTest Case Executions

First option: Import all the test cycles and test releases.

For Jira Xray and BrowserStack, a banner estimates how many API calls the import makes and how long it takes. Other integrations on that account can slow down while it runs.

  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.

The Map Users stage lists every user in the source project. Each one needs an Arcus user, who becomes the owner of their items. TestMuAI has no Map Users stage and goes straight to Map Fields.

  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.

Map Fields pairs values from your tool with Arcus values. 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.

Every tool maps Priority and Execution status. Some also map a third field:

  • qTest: Test case status.
  • TestRail and Testmo: Case type.
  • Jira Xray, BrowserStack, and Qase: Test case type.
  1. Review each field. To use an existing Arcus value instead of creating one, select it from the list.

  2. Click Begin Import.

The last stage is named for what your tool imports: Import of Test Cases, Cycles & Releases for qTest; Import of Test Cases, Milestones & Runs for TestRail and Testmo; Import of Test Cases, Plans & Executions for Jira Xray; Import of Test Cases, Cycles & Executions for Zephyr Scale; Import of Test Cases, Plans & Runs for BrowserStack, Azure DevOps Test Plans, 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.

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.

For qTest imports, you can also click Re-import. It starts a new import run that re-reads the qTest project and brings in anything new. In Re-import from qTest, choose what happens to test cases already imported that have changed in qTest:

  • Leave existing imports only new test cases. Nothing already in Arcus is modified.
  • Update existing updates changed cases in place and records the change in their history. Cases you edited in Arcus since the last import are reported and left untouched.

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.

Was this page helpful?