- Getting started
- About Test Manager
- Autopilot actions
- About Autopilot chat (agent)
- About PII Masking
- Test Manager feature availability
- Generating tests for requirements
- Linking test cases to requirements
- Assigning Studio automation to test cases
- Adding manual steps to test cases
- Uploading documents
- Managing test cases
- Analyzing results
- Test types in Test Manager
- 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
Assigning Studio automation to test cases
Assign a Studio automation published to an Orchestrator feed to a test case for automated execution.
Test cases in Test Manager can include both manual steps and a Studio automation. The automations are created in Studio as test cases, using the available activities. You need to assign Studio automations to test cases from Test Manager, to use automated executions.
Steps
- Publish the Studio project containing the automated test cases to the Tenant Package Feed, or to another Orchestrator folder feed.
- Open your desired Test Manager project.
- Go to Test Cases.
- Create a test case.
- In the Automation tab of the previously created test case, choose the Select Automation option.
-
From the Package Source dropdown list, select a feed from the corresponding Orchestrator instance.
This feed should contain the Studio test case you intend to link to the Test Manager test case. The default selection is Tenant Package Feed. Only folders with their own feeds appear in the Package Source dropdown list. In a folder hierarchy scenario, only the parent folder displays in the dropdown list as all subfolders share the same feed.
Note:The available package feed options are the ones for which you have administrative rights.
-
Select an automation from that location after you choose the package feed.
Note:The Test Case Name column displays the folder to which the automation was published to in Orchestrator, followed by the automation name. For example, if you want to select the
Create Checking Accounttest case that was published from Studio to theAccountsfolder in Orchestrator, the Test Case Name for this automation isAccounts/Create Checking Account.
-
- Select Save to confirm the changes.
Result
The selected automation is linked to the test case, with its name displayed under Test Case Name and the published package listed under Package.