Parameter substitutions enable you to easily substitute values in your script through the Synthetic Classic Portal and allow each individual Backbone node to be assigned its own value to use for a specific script parameter.
When can you use this scripting method?
The most frequent use for parameters is to work around concurrency issues with an application. For example, defining parameters by node lets you assign a unique login to each Backbone node from which to test your application.
Another use is when you need to frequently swap out a value in your script and you do not want to re-record or manually modify the script.
Parameters are exposed in the Synthetic Classic Portal, and can be edited in the Advanced Settings tab for the test. For details, refer to the test settings pages help pages.
Using this method
Parameters are stored in the script's JSON structure within an array named
<paramName> with the name assigned to the parameter you want to use.
Parameters can be referenced from within a Custom action as well as used within a standard action using the backtick method.
Selecting Apply Parameter in the FormFill and Type action panes auto-generates a reference to the parameter chosen from the list and automatically wraps the statement in backticks in order to be evaluated.
The agents recognize parameters defined using the parameter notation
:::IItokenII:::, where the token is replaced by the name assigned to the parameter. The following example parameter references are equivalent:
The syntax for each is valid in GSLv2. The first syntax, accessing via the parameters hash using backtick syntax, is preferred in GSLv2.