Troubleshooting automated executions

Common issues with automated test set executions in Test Manager, including missing Orchestrator package publications and test case linking errors.

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

You need to publish the Studio package to Orchestrator. This issue occurs when a test case is linked from Studio to Test Manager but the package is not yet published to Orchestrator.

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 test cases in a test set are not published in the latest Studio package to Orchestrator. You might get the same error when there is no process/release found on Orchestrator for the Studio package.

Automated execution could not start since no automated test cases could be found in this test set.

Solution

You need to have at least one automated test case to use Execute Automated. For more information, see Conditions.

Unable to start execution. No executable automated test case found with current package selection on the test set. Please try with a different package selection.

Solution

This error occurs when the test set's execution folder points to a different Orchestrator package feed than the one the test case's automation is linked to. A package published to two different folder feeds is treated as two distinct packages, so Test Manager cannot match them across feeds, even if a copy of the same package exists in the execution folder's feed.

To run test cases whose automations are linked to different feeds within the same test set, publish the relevant packages to a shared feed, such as the tenant-level feed or a dedicated end-to-end (E2E) feed, and link new test cases in Test Manager to the automations published there. For more information, see Selecting automation and Configuring test sets for specific execution folders and robots.

I cannot select test cases from a specific Orchestrator folder in Test Manager.

Solution

Folder visibility in Test Manager mirrors your Orchestrator folder permissions. If you don't have Orchestrator access to a folder, you will not be able to select test cases from that folder in Test Manager either. To make packages visible across multiple folders instead, publish them to a shared tenant-level feed, including the default "Tenant Package Feed" folder, rather than a folder-level feed.

Test Manager shows 0 runtimes available despite an assigned machine template.

Solution

Work through the following checklist:

1. Confirm Testing Runtimes are allocated to the tenant, under Host Tenant > Administration > Licenses.
2. Confirm the machine template has testing runtimes and is assigned to the correct folder.
3. For on-premises deployments, confirm TestAutomation.ModuleEnabled is active in UiPath.Orchestrator.dll.config.
4. Confirm the robot's Assistant is connected to that specific folder's machine template. Runtimes show as unavailable if it isn't, even when the template itself has runtimes assigned.
5. If all of the above check out, allow time for a cache or connection-state refresh before escalating further.

"Run test with Autopilot" fails at "Validating robot connection."

Solution

This is typically a machine or environment setup gap, not a licensing issue. Confirm the following, which mirror the prerequisites for running an automated test case in attended mode:

1. Confirm UiPath Assistant/Robot is installed on the same machine as the browser.
2. Confirm the robot service is running and signed in, connected to the same Orchestrator URL and tenant as the Test Manager service.
3. Confirm the machine and robot are present in the same folder configured in the project's Automation tab.
4. Confirm the UiPath browser extension is enabled.

The test execution is stuck in "Pending" and never starts.

Solution

This can occur for either of the following reasons:

• The machine assigned to the execution folder has only a NonProd robot runtime. NonProd runtimes cannot execute test cases, regardless of the user's roles or permissions. Assign a machine with a runtime type that supports test execution, such as Testing or Prod, and re-run the execution.
• The robot account configured on the machine has an incorrect domain or username. Verify the robot account's credentials in Orchestrator and correct them if needed.

There was an error executing the test set. Please try again.

Solution

If execution of the test set fails for any reason other than the ones specified above, get help from UiPath Support Services.