Troubleshooting

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.