- Getting started
- Project management
- Working with Change Impact Analysis
- Create test cases
- 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
Importing Orchestrator test sets (removed)
Reference for the removed import of Orchestrator test sets into Test Manager, which transferred test cases, schedules, results, and attachments.
This feature is removed. The Testing module in Orchestrator is no longer available, so you can no longer import Orchestrator test sets into Test Manager.
This topic describes the import process that was used to transfer test artifacts from Orchestrator to Test Manager.
For details on the removal, see the dedicated FAQ and the deprecation timeline.
What the import did
The import transferred test sets from an Orchestrator folder you had access to into a Test Manager project. It required the TestCase.Create, TestSet.Create, and TestExecution.Create permissions, which the Project owner and Test Manager roles have.
What was transferred
The import transferred the following details:
- Test cases: The test case data, including name, description, and activity coverage, was preserved. New test cases were created in Test Manager for the ones that were not linked yet, and versioned test cases kept their versions. Test cases that did not belong to a test set were not migrated.
- Test set arguments: Arguments configured for the Orchestrator test set were transferred as parameters, with their default values, to the corresponding imported test sets. Test case parameters remained unchanged.
- Execution folder: The imported test set kept the Orchestrator folder as the execution folder.
- Robot/User account: Any Robot or User account mapped to the Orchestrator test set was transferred to the test set in Test Manager.
- Test set schedules: All schedules associated with the Orchestrator test set were imported in a disabled state. To use these schedules in Test Manager, you had to reactivate them.
- Test results: The test execution results of the imported Orchestrator test sets were carried into Test Manager. Results that were not linked to an existing test set were not migrated.
Note:
- Duplicate test execution results generated in Test Manager after migration could affect existing integrations with Test Manager Connect, resulting in changes in dashboards and reports.
- If you use Test Manager Connect and the migration created a large number of artifacts, you may notice increased synchronization activity with external ALM tools integrated with Test Manager.
- Attachments: Any attachments tied to test cases within the imported Orchestrator test sets were transferred to Test Manager.
- Labels: Imported test sets were tagged with two labels:
orchestrator-importedandimported-<date>(for example,imported-17Jun2025). - Created and updated by: The imported test set is listed as created and updated by an
Externaluser.
To run an imported test set via a CI/CD pipeline task, refer to Running an imported test set via CI/CD.