Update Run mode

Relevant for: GUI tests and components

Update Run Mode runs the test or component to update the following:

  • The set of description properties used for test object descriptions

  • The Active Screen images and values

  • The expected checkpoint values

OpenText Functional Testing updates the set of description properties for each object class in your associated object repositories according to the properties currently defined in the Object Identification Dialog Box.

Example: Suppose you design a test or component for the English version of part of your application.

You now want to use the same test or component for the French version of your application.

To do this:

  1. Define a property that is not language-dependent, such as target, so that OpenText Functional Testing can use these properties instead of text-based properties for object identification.

  2. Perform an update run on the English version of this part of your application using these new properties.

  3. Run the test or component on the French version of your application.

Smart Identification

If your objects are identified using Smart Identification, you can use Update run mode to change the set of properties:

Objects identified using Smart Identification

If you have a test or component that runs successfully, but in which certain objects are identified using Smart Identification, you can change the set of properties used for object identification.

Then, use the Update test object descriptions option to update the test object description to use the set of properties that Smart Identification used to identify the object.

When you run the test or component with Update test object descriptions selected, OpenText Functional Testing finds the test object specified in each step based on its current test object description.

If OpenText Functional Testing cannot find the test object based on its description, it uses the Smart description properties to identify the test object (if Smart Identification is enabled).

After OpenText Functional Testing finds the test object, it then updates its description based on the mandatory and assistive properties that you define in the Object Identification Dialog Box.
Parameters or Regular Expressions

Any properties that were used in the previous test object description and are no longer part of the description for that test object class, as defined in the Object Identification Dialog Box, are removed from the new description.

This occurs even if the values were parameterized or defined as regular expressions.

If the same property appears both in the test object's new and previous descriptions, and the property value in the previous description was parameterized or specified as a regular expression, one of the following occurs:

  • If the previous value and the current value match ...... OpenText Functional Testing keeps the property's previous parameterized or regular expression value.

    For example, if the previous property value was defined as the regular expression button, and the new value is button1, the property value remains button.

  • If the previous value and the current value do not match ...... but the object is found using Smart Identification, OpenText Functional Testing updates the property value to the new, constant property value.

    For example, if the previous property value was button, and the new value is My button, if Smart Identification definition enabled OpenText Functional Testing to find the object, My button becomes the new property value.

    In this case, any parameterization or use of regular expressions is removed from the test object description.
Property Case-Sensitivity

In some cases, the case-sensitivity of some description properties may change from one version of OpenText Functional Testing to the next, or as a result of a patch or hotfix installation.

In those cases, when you use Update Run to update test object descriptions, OpenText Functional Testing also updates any case-sensitivity settings that may have changed.

Below is an example of the run results for a step in which the case-sensitivity of some description properties were updated from case-insensitive to case-sensitive.:

See also: