Migrating from other solutions

There is more than one kind of migration into Allure TestOps. Before you start, decide which of these three paths you actually need:

• bring manual test cases into Allure TestOps;
• onboard existing automated tests into Allure TestOps reporting;
• connect Allure TestOps with another TMS for synchronization or export.

1. Manual test case migration

Use this path when the main goal is to move existing manual test assets into Allure TestOps.

There are three main ways to migrate manual test cases:

• using an API (API-to-API);
• using CSV files;
• using other types of files (File-to-API).

Supported test management systems

If your current TMS supports exporting test cases to CSV files, you can import them using the Allure TestOps interface. This process is described in detail in the Import test cases from CSV files instruction.

Some TMSs allow you to export test cases to other file formats or fetch them via an API. In this case, we encourage you to create a ticket in our support system to get assistance from our engineers.

You can find a list of the supported TMSs in the table below.

2. Automated-test onboarding

Use this path when the tests already exist in code and you want Allure TestOps to build the visible automated test base from execution results.

In this case, you do not migrate manual test cases first. Instead, you:

1. include an Allure Framework adapter in the automated test code;
2. run the tests and produce result files;
3. upload those results to Allure TestOps.

For the full flow, see Running an automated test case and Run automated tests.

3. TMS synchronization and export

Use this path when the test assets should stay connected to another TMS after Allure TestOps is already in place.

This is not the same as importing historical manual cases once. It is an ongoing integration workflow for:

• external test keys;
• outbound export of cases or launches;
• synchronization between Allure TestOps and a connected TMS.

For those workflows, start with Test management sync and export.

When to contact support

If you have found your TMS in the list, after setting up your Allure TestOps instance, do the following:

1. Sign in to help.qameta.io and click Submit a ticket.

2. Fill in the fields:

   • In the Subject field, enter "Migration from <Name and version of your TMS>".
   • Choose your deployment type.
   • Select "Support" as the request type.
   • In the Description field, enter any additional information that might be useful.

3. Click Submit.

Once our support team responds to the ticket, follow their instructions to complete the migration.

Next steps

• Import test cases from CSV files for manual-case import.
• Running an automated test case for automated onboarding.
• Test management sync and export for external TMS integration workflows.