test-manager
latest
false
- Getting started
- Project management
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Troubleshooting
Executing automated tests

Test Manager user guide
Last updated Aug 26, 2025
You can execute all test sets using Execute Automated. Orchestrator is invoked for test cases that have been linked to Test Manager. To execute test sets linked from Orchestrator, make sure you create your test sets in Orchestrator.
You can also execute automated test if the test set includes test cases linked from Studio. For more information, see Executing Tests.
Important: To use the Execute Automated option,
you need at least one automated test case in a test set.
- Automated test executions have a default timeout of four days, that you cannot change. Any automated test execution that exceeds four days is marked as Cancelled.
- Test execution for test sets linked from Orchestrator includes only the test cases that have been published to the Orchestrator Tenant Process Feed in the latest package version. If you want to execute new test cases, you need to publish a new package version in Orchestrator, and then link the test set to Test Manager.
- If your Test Manager test set includes test cases
from multiple Studio projects, then the project that has the highest number of
test cases is considered for execution. Therefore, only the test cases from this
project will be executed. In this case, you will receive the following message
within Test Manager: "Test cases from multiple packages have been selected. Some
of the test cases will not execute while running this test set."
You can execute test sets including test cases from multiple Studio projects, only if you have a test set linked from Orchestrator.
- If your test set includes test cases that are duplicate in multiple Studio projects, the sorting is done by the project name in descending order. Only the test cases from the project that is placed first in the list will be executed.