- 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
- Document test cases with Task Capture
- Parameters
- 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
- Applying filters and views
- Accessibility testing for Test Cloud
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- ALM tool integration
- Test Manager Connect
- Test Manager - Integration Service connector
- Outbound IP ranges for connectors
- SAP Cloud ALM
- Setup and configuration
- Step 1: Configuring user machine
- Step 2: Configuring SAP Solution Manager
- Step 3: Configuring system under test
- SAP Solution Manager command line
- Use case scenarios
- SAP test automation best practices
- Troubleshooting the Jira integration
- Webhooks
- API integration
- Coding Agents for Testing
- Troubleshooting
Step 3: Configuring system under test
Configuration reference for setting up users and authorizations in a System Under Test to enable automated test execution through Test Manager.
To perform test automation in your System Under Test (SUT), you need to set up the right user and assign the correct authorizations.
Set up communication users
The SUT needs the ECATT_ET_USR communication user, which you create manually.
Steps
- Create ECATT_ET_USR in transaction SU01.
- Set the user type to System.
- Set the same password for both users, in SAP Solution Manager and in the SUT, to ensure seamless integration.
Result
The ECATT_ET_USR communication user exists in the SUT with the user type System, and its password matches the one in SAP Solution Manager.
Enable SAP GUI scripting
Studio and Robots require SAP WinGUI scripting to be enabled on the local machine as well as on the server side, before you create your first automation projects for SAP.
Steps
- Go through the SAP WinGUI configuration steps.
Result
SAP WinGUI scripting is enabled on the local machine and on the server side.
Enable ECATT
Each client where testing takes place must allow eCATT to be executed.
Steps
-
Start transaction SCC4.
-
Select the corresponding clients.
-
Go to Details.
-
Under the CATT and eCATT Restrictions section, set eCATT and CATT to Allowed.
-
Select Save to confirm changes.
Result
eCATT and CATT are allowed on the selected clients. The System Under Test is ready for automated test execution through Test Manager.