Troubleshooting

Automation already linked to another test case in Test Manager

Issue description

If you attempt to link a Studio test case that's already linked to a different Test Manager instance than the one you're currently working in, you receive the following error: "Automation already linked to another test case in Test Manager".

Solution

You cannot directly unlink the test case. However, you can work around this by converting the test case to a workflow and then converting it back to a test case. This process changes the test case ID, allowing it to be linked to your current Test Manager instance, but without modifying the underlying logic of the test case.

Visit Convert workflow to test case for information about converting a workflow into a test case.

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.