- 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
Creating automated tests
Create, publish, and link automated tests in Studio before running them as part of performance scenarios in Test Manager.
Before running performance scenarios, you must create, publish, link and assign your tests.
Prerequisites
- You can create performance scenarios only for test cases built using the latest supported packages (
Testing.Activitiesv.25.10.2 or higher,UIAutomation.Activitiesv.25.10.2 or higher,WebAPI.Activitiesv.2.1.0 or higher). Older versions may work locally or in test sets but fail when executed at scale. - Use Windows projects when you execute test cases on-premises, using App Testing robots (unattended robots).
- Use Cross-platform projects when you execute test cases using serverless robots. You cannot run desktop automations, such as for SAP WinGui, on Cross-platform projects.
Steps
-
Create tests in Studio. Configure the tests.
- Design your automated tests as you would for any functional test case.
Note:Whichever project type you use, Workflow Analyzer runs automatically as part of every dry run and checks each test case for two things: whether the package versions above are met, and whether the automation uses any activities that aren't eligible for performance testing. If a check fails, Workflow Analyzer reports what's wrong so you can fix it before spending robot minutes on a run that can't succeed.
Unsupported activities include:
- Computer vision activities
- Image-based/OCR activities
- Hardware Events input mode
- Local file system access
- Desktop-only interaction patterns, such as global hotkeys and window management
For examples on creating various automated tests in Studio, see the following tutorials:
Tip:Run your automated tests locally in Studio to validate behavior before deploying it for performance testing, as tests must be data-stable and reliable before scaling.
-
Publish your project containing the automated tests to Orchestrator. The project is published to Orchestrator under the form of a NUPKG package. For steps on publishing Studio project to Orchestrator, refer to About publishing automation projects.
-
Link tests to Test Manager.
- Go to Test Manager, in the same tenant where you published the project to Orchestrator.
- Create a test case. Refer to Create test cases for detailed steps.
- Open the previously created test case, and select Select automation to link the previously published NUPKG package, containing the Studio automated tests. Refer to Selecting automation for detailed steps on selecting an automation for a test case.
-
Assign tests to test sets in Test Manager. Refer to Adding test cases to a test set for detailed steps.
-
Run the test case in a test set in Test Manager to confirm successful execution. Refer to Executing automated tests for detailed steps.
Result
The automated test cases are created, published to Orchestrator, linked to Test Manager, and assigned to test sets. The tests are ready to be executed as part of performance scenarios.