How do I get the Migration Tool?
You can download the new qTest importer tool from the SpiraTest Add-Ons and Downloads section:
How does the Migration Work?
The migration tool is a simple wizard that connects to qTest via its REST API and downloads all the Users, Test Cases, Test Sets, Test Runs, Issues, Requirements and Attachments from qTest . It then connects to SpiraTest using its SOAP API and imports the corresponding data seamlessly and effortlessly into SpiraTest.
The migration tool will import the following artifacts from qTest:
- Project name
- Users with a default password (but not their roles and permissions)
- Requirements
- Releases
- Test cases with their steps (if defined)
- Test Sets
- Test Runs
- Defects
- Modules (these will be imported automatically as Test Case folders and also as Requirement epics)
- Test Cycles (these will be imported automatically if Test Sets are imported, and will be imported as Test Set folders)
- Attachments for Releases, Requirements, Test Cases, Test Steps and Defects
- Associations between Releases, Requirements, Test Cases, Test Runs, Test Steps
How Does The Data Look?
To give you an idea of how the data migrates between the two systems, here are some screenshots of how the requirements, test cases, test sets, and defects look in the two systems:
Requirements
When you migrate requirements from qTest that look like this:
They will appear in SpiraTest like this:
Releases
When you migrate releases from qTest that look like this:
They will appear in SpiraTest like this:
Test Cases
When you migrate test cases from qTest that look like this:
They will appear in SpiraTest like this:
Test Sets
When you migrate test sets from qTest that look like this:
They will appear in SpiraTest like this:
Test Runs
The Test Runs migrated in this example from qTest will be displayed in SpiraTest like the following:
Defects
When you migrate defects from qTest that look like this:
They will appear in SpiraTest as incidents like this:
Where Can I Learn More?
For more information on using the Tricentis qTest importer, please refer to the Migrating from Tricentis qTest Guide.