ALM Tool Integration

Test Manager supports two ALM integration patterns with external tools. The integration patterns are independent of the CI/CD pipeline integrations.

This integration pattern is useful for scenarios where external ALM tools for defect management, agile planning and requirements management are already in place but lack test management capabilities. This way of integration makes use of Test Manager for managing tests and results while integrating the testing process into the development lifecycle supported by the external toolset.

In the following diagram, you can view which tasks are performed by which component (external or UiPath) for this ALM integration pattern. The direction of a relationship between the components is indicated by the arrows.

In a real-life scenario, you will be using Studio to create automation and assign it to your tests, followed by test execution performed by Orchestrator, with the results being pushed to Test Manager for analysis and integration into the development process. In the context of a failed test, as a result of a test execution, you might want to create a defect. If you have an external tool for defect management, you can use Test Manager to create this new defect. The defect will be created in your tool and linked to all affected requirements. The defect will be enriched with detailed log information from the executing robots.

You can use this integration pattern to automate and execute your tests through Studio and Orchestrator, respectively, while using your external tools to create and manage the tests. Through this integration pattern, you will be using external tools for test management and only the server component of Test Manager (Test Manager Hub) will allow using automation in test cases created in the test management solution of your choice.

In the following diagram, you can view which tasks are performed by which component (external or UiPath) for this ALM integration pattern. The direction of a relationship between the components is indicated by the arrows.

For example, you can use Studio to assign automation to your test cases, execute them through Orchestrator, and then push the results directly to your external tool (e.g. Xray for Jira). Execution results are uploaded to Test Manager Hub and then pushed to your external tool through the connectors.

The connectors are libraries that connect external ALM tools with Test Manager. A generic interface defines how an external system is to be integrated. The connectors are out-of-the-box and provide the specific implementation of this interface in order to integrate certain ALM systems.

You can configure the connectors in Test Manager for each project, individually. Any number of external systems and projects can be integrated with Test Manager.

The following table lists the connectors that bridge external tools to Test Manager.