- 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
- Creating parameters
- Editing parameters
- Using parameters in manual testing
- Best practices for test case arguments and data
- 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
Using parameters in manual testing
Reference parameters in manual test steps and override their values across test sets or automated executions.
Use parameters in the steps of a manual test case.
Context
- You can use parameters in manual or automated testing with the default values that you set for each test case. Or you can override the default parameter values for the test cases within a test set. For details, see Overriding parameters.
- Manual test cases support only a single default value per parameter. There is no built-in way to define multiple value sets (an iteration or parameter table) for one manual test case. To run a manual test case against different parameter values, create separate test sets, each overriding the parameter to a different value for that test case.
- During the automated execution of a test set, the Studio arguments from the automation (corresponding to each test case) are automatically applied (as parameters) in Test Manager, at test-set level for each test case added in the test set.
- For automated executions, Studio arguments are surfaced in the Override parameters view at the test-set level. They do not appear in the Parameters tab of an individual test case, which is reserved for parameters that you manually create in Test Manager.
- Test Manager parameters are always of type String. Because of this, data is passed from Test Manager to a Studio argument only when that argument is also of type String. If the Studio argument uses a different data type, the value is not passed, even if the names match.
Test Manager parameters do not automatically map to Studio arguments, even when the names match, and there is no global variable shared across test cases in a test set. Arguments, defined in Studio and overridable at the test-case or test-set level, are the supported mechanism for passing values between test cases. Test Manager does not aggregate test-case data at the test-set level natively; for test-set-level reporting, use an external reporting tool.
Steps
-
Create a new test case.
-
Go to the Manual Steps tab and add manual steps.
-
To reference parameters in the manual steps, enter their name between double curly brackets. For example, to add the
usernameparameter inside a manual step, reference it as{{username}}.
Result
The test case references the parameters you added, and the values are applied when the test case is executed.