Properties and operations for test objects and run-time objects

Relevant for: GUI tests and components

UFT uses unique terms to differentiate between the properties and operations for test objects, which are the objects that UFT creates to represent the objects in your application, and the properties and operations for run-time objects, which are the actual objects in your application. The table below introduces some of these terms.

UFT Test Objects

Run-time Objects From Your Application

description properties are UFT-specific properties that UFT uses to identify objects in applications, to retrieve and store information about those objects, or to compare stored values with the current values of an object in an application.

The description properties available for a test object are determined by its test object class (and not by the actual properties available for the object in the application).

Native properties are the properties created by the object creator for each run-time object. (Examples of object creators include Microsoft for Microsoft Internet Explorer objects and the product developer for ActiveX objects.)

A test object operation is a method or property that UFT can perform on an object from a particular test object class.

Example: UFT can perform the Click method on a WebButton test object.

Native operations are the methods of the object in your application as defined by the object creator.

As you add steps to your test or component, you specify which operation to perform on each test object. If you record steps, UFT records the relevant operation as it is performed on an object. During a run session, UFT performs the specified test object operation on the run-time object.

You can view and modify properties and operations for test objects and run-time objects in a number of ways:

Test objects
  • Retrieve or modify values manually while designing your test or component, or use SetTOProperty statements during a run session.

    For details, see Test Objects in Object Repositories, Retrieving and setting values, and the SetTOProperty method in the Common Methods and Properties section of the UFT Object Model Reference for GUI Testing.

  • Use regular expressions in function libraries to identify property values based on conditions or patterns you define. For details, see Regular expressions.

  • Parameterize values with data table parameters so that a different value is used during each iteration of the test. For details, see Parameterizing Object Values.

  • View or modify the values that are stored with your test or component in the Object Properties or Object Repository window. For details, see Maintaining description properties.

  • View the current values of any visible object using the Properties tab of the Object Spy. For details, see Use the Object Spy.

  • You can view the syntax of the test object operations of any visible object using the Operations tab of the Object Spy. For details, see Use the Object Spy.

Run-time objects
  • View the syntax of the native operations of any visible object using the Operations tab of the Object Spy. For details, see Use the Object Spy.

  • Retrieve native property values from the run-time object during the run session by adding GetROProperty statements. For details, see Retrieving and setting values.

  • If the available test object operations and description properties do not provide the functionality you need, access the internal operations and native properties of the run-time object using the Object property. You can also use the attribute object property to identify Web objects in your application according to user-defined properties. For details, see Native properties and operations and the Objectproperty in the Common Methods and Properties section of the UFT Object Model Reference for GUI Testing.

  • When using Insight test objects, which UFT recognizes in the application based on the object's appearance, UFT does not use the object's programming interface and therefore native operations and properties are not relevant.