- Getting started
- Project management
- Documents
- 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
- Manual test cases
- Importing manual 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
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governeed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Applying filters and views
- Importing Orchestrator test sets
- Creating test sets
- Adding test cases to a test set
- Assigning default users in test set execution
- Enabling activity coverage
- Enabling Healing Agent
- Configuring test sets for specific execution folders and robots
- Overriding parameters
- Cloning test sets
- Exporting test sets
- Applying filters and views
- Accessibility testing for Test Cloud
- Searching with Autopilot
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Troubleshooting
Test Manager user guide
Creating parameters
You can create parameters for each test case within a test set. You can add a maximum number of 250 parameters, each required to have a unique name in the context of a test case.
Parameters can only be of type String.
- Open the test case to which you want to add parameters.
- Go to the Parameters tab.
- Select Create Parameter and fill in the fields below:
- Name - Give the parameter a unique name.
When you name the parameter, you can use letters, numbers, spaces, and the following characters: -, _, ,, and ..
For example, name the parameter as adminName.
2. Default value - Type the default value of the parameter.
Remember that parameters can only be of type String.
This Default value field is not mandatory, so if you leave it empty, then the parameter will be an empty string.
For example, set the default value to JohnDoe.
3. Hint - Offer additional information about the information that the parameter holds.
For this example, add the following hint: The supervisor of the organization.
4. Select Create to create the parameter.
Editing parameters
After you create parameters, you can edit them, according to your use case.
- Open the test case for which you want to edit a parameter.
- Go to the Parameters tab.
- Select Edit next to the parameter that you want to edit.
- In the Edit Parameter window, update the fields that you want to change.
- Select Save to save the changes.
Using parameters in manual testing
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 information on overriding parameter values, visit Overriding parameters.
- Create a new test case.
- Depending on the execution type you want to use, follow these steps:
- Manual execution:
- Go to the Manual Steps tab and add manual steps.
- To reference parameters into the manual steps, input their name between double curly brackets.
- Manual execution:
For example, to add the username parameter inside a manual step, reference it as {{username}}.
- Automated execution: 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.
In Test Manager, parameters created for test cases do not automatically map to the arguments defined in the Studio automation, even if they share the same name. Test Manager parameters operate independently from the arguments defined in Studio. When you create a parameter in Test Manager, it does not automatically pass its value to the Studio automation during execution. The intended workflow is to use overriding parameters from the test-set level.