Migrate ReqTest to Azure DevOps Test Plans

Introduction

The ReqTest to Azure DevOps Migrator is a CLI tool from Solidify (now Eficode) which facilitates transfer of all of your test data from the ReqTest platform to Azure DevOps Test Plans. This blog post introduces the tool and guides you through how to migrate all test data from ReqTest to Azure DevOps (AzDo) Test Plans, ensuring a smooth transition and maintaining test integrity.

The tool is ideal for organizations aiming to seamlessly switch their test management platforms, or simply evaluate Azure DevOps Test Plans while maintaining test integrity.

Notice on obtaining the tool

This blog post uses the ReqTest to Azure DevOps Migrator from Solidify. If you are interested in obtaining the tool for evaluation purposes, feel free to contact us

Tool capabilities

Our tool supports all the following ReqTest resources:

• Test Cases: All test cases are accurately migrated.
• Requirements: Transfers requirements to maintain project coherence.
• Bugs: Transfers bugs to streamline the development process.
• Test Suites: Transfers test suites and maintains the test suite hierarchy.
• Test Runs: Complete migration of previous test runs and their outcomes.

Procedure overview

1. Grant necessary permissions in Azure DevOps
2. Obtain API tokens
3. Configure the CLI tool
4. Set up the user map
5. Run the CLI tool
6. Verify the results

1. Step by step: Set permissions and obtain API tokens

Azure DevOps

License notice

In order to access Azure Test Plans and exercise the full range of test-related features, you must have been granted Basic + Test Plans access level or have one of the following subscriptions: Visual Studio Enterprise, Visual Studio Test Professional or MSDN Platform.

Necessary permissions

The same user who will run the migration will require Contributor access to the desired Azure DevOps project, as well as the following permissions on project and area path level:

Project level:

• Create test runs
• Manage test configurations

Area path level:

• View work items in this node
• Edit work items in this node
• Manage test plans
• Manage test suites

PAT scopes

When creating your Personal Access Token (PAT), you will need to enable the following scopes:

• Work Items: Read, write, & manage
• Test Management: Read & write

Now you may create a PAT and store it somewhere secure.

2. Step by step: Configuration

You will find all necessary configuration at the top of the migrator.py file.

Configuration description

• reqtest_project_id: ReqTest project ID (numeric value).
• reqtest_api_key: ReqTest access token for authentication.
• azdo_collection_url: URL to your Azure DevOps organization.
• ado_project: Name of your Azure DevOps project.
• azdo_pat: Azure DevOps Personal Access Token for authentication.
• azdo_testplan_id: Azure DevOps Test Plan ID (numeric value).
• azdo_testplan_rootsuite_id: ID of the suite under the AzDo test plan where test cases should be placed (numeric value).
• azdo_areapath: Azure DevOps area path for proper categorization.
• azdo_iterationpath_base: Azure DevOps iteration path for organized planning.
• usermap_path: File path to the user map, defining mappings between ReqTest and AzDo users.

Example configuration

###################
## Confiugration ##
###################

reqtest_project_id = 123456789
reqtest_api_key = "your_reqtest_api_key"
azdo_collection_url = "https://dev.azure.com/yourorganization"
ado_project = "Your_Azure_DevOps_Project"
azdo_pat = "your_azure_devops_personal_access_token"
azdo_testplan_id = 987654321
azdo_testplan_rootsuite_id = 456789012
azdo_areapath = "Your_AzureDevOps_AreaPath"
azdo_iterationpath_base = "Your_AzureDevOps_IterationPath"
usermap_path = "C:\\path\\to\\your\\usermap\\file.txt"

3. Step by step: User map

The user map will govern which Azure DevOps identity becomes tied with which user in ReqTest. This will affect the work item assignee field, as well as the work item history and comments.

All of your active ReqTest users will need to be present in the user map file. The file needs to have the name user-map.txt, and it should follow this format:

reqtest.user1@email.com=azdo.user1@email.com
reqtest.user2@email.com=azdo.user2@email.com
reqtest.user3@email.com=azdo.user3@email.com

4. Step by step: Run the tool

Once all the configuration is set up, simply run the tool with the following command:

python3 migrator.py

The tool will perform an online migration by posting all data directly to Azure DevOps.

After successfully migrating all test data, take a moment to review the log and ensure that there were no errors during the migration.

Conclusion

This blog post has introduced the ReqTest to Azure DevOps Migrator from Solidify, which lets you migrate all of your test data from the ReqTest platform to Azure DevOps Test Plans.

If you would like to make a product inquiry, or if you have any other questions, contact us.