- Getting started
- Project management
- Working with Change Impact Analysis
- Create test cases
- Assigning test cases to requirements
- Cloning test cases
- Exporting test cases
- Linking test cases in Studio to Test Manager
- Delete test cases
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Enabling or disabling governance in bulk for test cases
- Enforcing signing order for governed test cases
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Viewing governance information for test case logs
- Managing approvers for governed test case logs
- Managing governed test case logs in the In Work state
- Managing governed test case logs in the In Review state
- Managing governed test case logs in the Signed state
- Managing comments for governed test case logs
- Enabling governance at test case log level
- Disabling governance at test case log level
- Viewing and searching test cases
- Project operations and utilities
- Test Manager settings
- Tenant level settings
- General project settings
- Events
- Subscribing to events
- Subscribing to all events
- Unsubscribing from events
- Unsubscribing from all events
- Unsubscribing from the Notifications settings page
- Viewing notifications
- Filtering notifications
- Viewing email notifications
- Enabling email notifications for SMTP servers
- Viewing only unread notifications
- Marking all notifications as read
- Clearing all notifications
- Deleting notifications
- Customer managed keys encryption
- Audit logs
- ALM tool integration
- ALM tool integration
- Test Manager Connect
- Test Manager - Integration Service connector
- Outbound IP ranges for connectors
- Working with SAP Cloud ALM and Test Manager
- Step 1: Integrating SAP Cloud ALM with Test Manager
- Step 2: Creating automated test cases in SAP Cloud ALM
- Step 3: Creating automated test cases in Test Manager
- Step 4: Synchronizing test cases from Test Manager to SAP Cloud ALM
- Step 5: Assigning test automations to test cases
- Step 6: Executing test cases
- SAP test automation best practices
- Troubleshooting the Jira integration
- API integration
- Coding Agents for Testing
- Troubleshooting
Executing automated tests
Execute automated test sets in Test Manager via Orchestrator, with support for live streaming, remote control, and video recording of executions in Test Cloud.
You can execute all test sets using the Execute > Execute Automated option from the Overview tab of a test set. This option invokes Orchestrator for test cases created in Test Manager.
You can also execute automated tests if the test set includes test cases linked from Studio. For more information, check Executing Tests.
Context
- 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 published to the Orchestrator Tenant Process Feed in the latest package version. To execute new test cases, publish a new package version in Orchestrator, and link the test set to Test Manager.
Important:
For any tenant, test management capabilities have been moved to Test Manager. As a result, test schedules are no longer available in Orchestrator, and you cannot execute test cases and test sets directly from Orchestrator anymore. As of July 31, 2026, this is also no longer possible through Orchestrator APIs for Test automation — use Test Manager instead.
- The following information is applicable only if you are using the legacy execution context in 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. As a result, only the test cases from this project will be executed. Additionally, Test Manager will display a warning stating that multiple packages have been selected, and only some of them will be executed. You can execute test sets including test cases from multiple studio projects only if you link Studio automations to Test Manager test cases using only the Configure Automation functionality.
- If your test set includes duplicate test cases 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.
Prerequisites
To use the Execute Automated option, you need at least one automated test case in a test set.
To execute automated tests while the Allow legacy execution context setting is disabled, you need the following permissions in Orchestrator:
- At the tenant level: Folders.View and Users.View.
- At the folder level, where the test automation package was published: TestSets.Create and TestSetExecutions.Create.