- 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 package and version
Select a specific package and version for test cases in a test set, either automatically or by manually adding each automation.
In addition to the execution folder and robot account, you can also select a specific package and version from which to run test cases.
Steps
-
Navigate to Test Sets and open a test set.
-
Go to the Test Cases tab.
-
Select Configure Automation.
-
Select one of the following options to define a package and version:
- Autoselect Packages: Automatically selects all packages located in the execution folder and their latest versions, based on the test cases assigned to the test set.
- Add automation: Lets you manually select the desired packages and corresponding versions. Use the following steps:
- From the Package dropdown list, select a package.
- From the Version dropdown list, select a version for that package.
- Use Select to finalize the selection. Repeat the previous steps for each package you want to add to the test set.
Figure 1. Display of Selected Automations menu illustrating the chosen execution folder and robot account, associated packages, and their respective versions for a specific test set
Result
The test set is configured to run its test cases using the selected package and version, either autoselected from the execution folder or manually chosen for each automation.