Solve individual test object description problems

Relevant for: GUI tests and components

Choose one of the following methods of fixing the test object description:

  • If you know that the new description in your application is a permanent or long-term change, you can manually modify the property's constant value.

    For details, see Maintain test objects in an object repository.

  • If the value of the property depends on a previous step or another object, parameterize the object property, so that it uses the output values from another step.

    For details on parameterization, see:

    For details about output values, see: Output values in GUI testing.

  • If you expect part of the property value to stay constant, while other parts change dynamically, modify the property value using a regular expression.

    For details on regular expressions, see Regular expressions.

  • If you expect the property to change regularly or in an unpredictable way, remove the property from the test object description and add one or more additional properties that will enable OpenText Functional Testing to uniquely identify the object.

    For details, see Remove properties from a test object description and Add Properties Dialog Box.

  • If you can only access the information on the property values during the run session, you can use programmatic descriptions to identify the object using property values retrieved earlier in the run session.

    For components: You use programmatic descriptions inside user-defined functions.

    For details on programmatic descriptions, see Programmatic descriptions.

  • If your object was unique when it was learned, but there are now two or more objects in your application with identical properties except for their location on a page (such as identical logo images in a Web page), add an ordinal identifier (index or location) to the test object description in the Object Properties or Object Repository window. For details on ordinal identifiers, see Ordinal identifiers.