Troubleshooting Test Manager

Solutions for common Test Manager errors, including CI/CD pipeline failures caused by test sets imported from Orchestrator.

Cannot use Test Set migrated to Test Manager

Error message

If you attempt to execute a Test Manager test set that was imported from Orchestrator using the Import test sets capability, through a CI/CD pipeline task, then you receive an error specifying that the CI/CD pipeline cannot use the test set because it was migrated to Test Manager.

Solution

To work around this limitation:

1. Go to the Testing tab in Orchestrator.
2. Clone the imported test set that you want to execute.
3. Use the clone for executing the test set through a CI/CD pipeline task instead of the original imported test set.
   Note:

   Cloning a test set does not copy its execution history. To preserve recent execution data within Test Manager, we recommend that you import the cloned test sets into Test Manager after running it via CI/CD.

Automated execution could not start since the package was not found on Orchestrator

Error message

Automated execution could not start since the package was not found on Orchestrator. Only test cases from packages which have been published to Orchestrator can be executed.

Solution

This issue occurs when you execute tests in Test Manager by triggering Execute Automated.

To address this issue, make sure that you have published the package to the Orchestrator Tenant Process Feed.

Test cases could not be executed since no executable versions could be found

Error message

Test cases could not be executed since no executable versions could be found. Only test cases published with the latest package version to Orchestrator can be executed.

Solution

This issue occurs when you execute tests in Test Manager by triggering Execute Automated.

To address this issue, make sure that you have published the package with the latest test case changes to the Orchestrator Tenant Process Feed.

This issue can also be triggered by a test case from your project that is linked to a different Test Manager project. To sort this issue, unlink the automation in Test Manager.

Test set contains test cases from multiple packages

Error message

Unable to execute. Test set contains test cases from multiple packages which is not supported.

Solutions

1. Duplicated Studio project locally: If you duplicated a Studio project locally by copying the project folder, take the following steps:
   1. Duplicate the faulty test case within Studio.
   2. Delete the original test case from the project.
   3. Re-publish the project to Orchestrator,
2. No local Studio project duplicated: If you did not duplicate a Studio project locally, relink the faulty test case to the test set.

No license found for Test Manager

Error message

No license found for Test Manager. Functional limitations apply.

Cause

This issue occurs when you enabled the Test Manager platform license, but you don't have a Tester - Named User license.

Solution

To address this issue, ensure that you have a Tester - Named User license assigned to your user account. For more information about licensing for using Test Manager, visit Unified Pricing: Licensing Test Manager.

Change Impact Analysis data source not visible after import

Cause

The /UIPATH/ ICF node (/sap/opu/odata/UIPATH/) that Change Impact Analysis depends on is created during the Heatmap transport request import. If this node is not visible after importing the Change Impact Analysis transport request, the most common cause is that the Heatmap transport request was not imported, or was not imported first.

Solution

Import the Heatmap transport request (S4HK903140), then the Change Impact Analysis transport request (S4HK903142). For more information, see Installing the UiPath SAP Add-On in your SAP system.

Autonomous Exploration fails with "Failed to start browser"

Error message

Failed to start browser. Extension native host is running, but new opened tab not found.

Cause

Autonomous Exploration opens the browser in incognito mode. If the UiPath browser extension is not allowed to run in incognito mode on the machine hosting the run, the native host starts but no browser tab opens, and the run fails. There is no registry or Group Policy setting that grants this automatically. It must be toggled manually in each browser.

Solution

On the machine running the robot, whether a local machine or a Cloud VM:

1. Open chrome://extensions in the browser.
2. Select Details on the UiPath extension.
3. Turn on Allow in Incognito.

Repeat this on every machine that can host the run. This is specific to Autonomous Exploration. Autonomous Test Execution does not run in incognito mode and is not affected.