Relevant for: GUI tests and components
Repository parameters enable you to specify that certain property values should be parameterized, but leave the actual parameterization to be defined in each test or component that is associated with the shared object repository that contains the parameterized values.
Repository parameters are useful when you want to create and run tests and components on an object that changes dynamically. An object may change dynamically if it is frequently updated in the application, or if its property values are set using dynamic content, for example, from a database.
If you delete a repository parameter that is used in a test object definition, the value remains mapped to the parameter, even though the parameter no longer exists. Therefore, before deleting a repository parameter, you should make sure that it is not used in any test object descriptions, otherwise tests or components that have steps using these test objects will fail when you run them.
Example: Suppose you have a button whose text property value changes in a localized application depending on the language of the user interface.
You can parameterize the name property value using a repository parameter, and then in each test or component that uses the shared object repository you can specify the location from which the property value should be taken.
For example, in one test or component that uses this shared object repository you can specify that the property value comes from an environment variable or a component parameter, respectively.
In another test or component it can come from the Data pane or a local parameter, respectively. In a third test or component you can specify it as a constant value.