test-manager
latest
false
Test Manager user guide
- 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
- Viewing and searching test sets
- Assigning default users in test set execution
- Enabling activity coverage
- Selecting an execution folder and account
- Selecting a specific package and version
- Selecting a specific host machine
- Best practices for configuring test sets
- Overriding parameters
- Cloning test sets
- Exporting test sets
- 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
Selecting a specific host machine
Select a specific host machine to enforce execution for all test cases in a test set when using Test Cloud.
Run the executions of a test set on one host machine in Test Cloud. If the selected host machine is not available, the execution waits and then times out.
Note:
This feature is available in Test Manager only when delivered through Test Cloud.
Steps
- Navigate to Test Sets and open a test set.
- Go to the Test Cases tab.
- Select Configure Automation.
- Select an Orchestrator execution folder.
- Under Runtime type, select one of the options, depending on your license type: Testing, App Testing, Cloud – Serverless Testing, Cloud – Serverless, Cloud – VM Testing, Cloud – VM.
- Under Robot account, select a robot account. The default value is Any User/Robot account, which executes the test set using any robot available in the selected folder.
- Under Machine template, select Any Machine or a specific machine template. The Host Machine field becomes available.
- Under Host Machine, select Any Connected Machine or a specific host machine.
- (Optional) Select or define a package and a version.
- Select Save to confirm the selection.
Result
The test set is configured to run all its test cases on the specified host machine, using the selected execution folder, runtime type, robot account, and machine template.