- Getting started
- Project management
- Documents
- Working with Change Impact Analysis
- Searching with Autopilot
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Troubleshooting
Test Manager user guide
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.
Solution
You need to have at least one automated test case to use Execute Automated. For more information, see Conditions.
Solution
If execution of the test set fails for any reason other than the ones specified above, get help from UiPath Support Services.
- Troubleshooting automated executions
- 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.
- 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.
- Automated execution could not start since no automated test cases could be found in this test set.
- There was an error executing the test set. Please try again.
