Import project

Import a TMH file from an external system into Test Manager as a new or existing project, migrating requirements, test cases, test sets, and attachments.

You can import projects from external sources to conduct testing operations through Test Manager. Use this feature to transfer entire testing projects from different Application Lifecycle Management (ALM) systems to Test Manager.

For more information, see the following topics:

• Getting the schema version
• Preparing the TMH file
• Importing a project in Test Manager
• Importing into an existing project in Test Manager
• Viewing automation information

How it works

Importing the project follows a schema that converts external system projects (e.g., testing applications) into a format that can be read by Test Manager. This includes objects such as requirements, test cases, test sets, test results, labels, custom fields, preconditions, postconditions, and attachments. The import process is done asynchronously.

Considerations

• New Object IDs (GUIDs) are generated during import in Test Manager.
• Time stamps (Created Time, Updated Time) are maintained.
• Created By, and Updated By refer to the user who submitted the project import request. We do not maintain the original user who created the artifact in the ALM system.
• File attachments exceeding the size limits (90 MB) are skipped.
• Automation links are not carried over during import, because linking depends on automation IDs that are unique to each tenant.

Note:

After importing a project into a different tenant, unlink and re-link each test case's automation to the corresponding automation in the destination tenant's Orchestrator. Otherwise, automated executions for that test case stay stuck in a pending state.

Who can import projects

Any user having a valid Test Manager License can import projects.

For more information see User and Group Access Management.

Related articles

• TMH file format specification