Repository parameter value mappings

Relevant for: GUI tests and components

You use repository parameters to specify that certain property values of an object in a shared object repository should be parameterized, but that the actual values should be defined in each action or component associated with the shared object repository.

After defining the repository parameter, mapping a repository parameter specifies that the property values are taken from:

  • Data table

  • random number

  • environment

  • test or action parameter

  • local parameter

  • component parameter

For example, you may want to retrieve the username object's text property value from an environment variable parameter for one test or component, and from a constant value, Data pane parameter, or local parameter for another.

Before you map repository parameters, if you have more than one repository parameter with the same name in different shared object repositories that are associated with the same action or component, the repository parameter from the shared object repository with the highest priority (as defined in the shared object repositories list) is used.

If you do not map a repository parameter, the default value that was defined with the parameter, if any, is used during the run session. If the parameter is unmapped, meaning no default value was specified for it, the test or component run may fail if a test object cannot be identified because it has an unmapped parameter value.