How virtual objects are defined and recognized

Relevant for: GUI tests and scripted GUI components

OpenText Functional Testing identifies a virtual object according to its boundaries. Marking an object's boundaries specifies its size and position on a Web page or application window. When you assign a test object as the parent of your virtual object, you specify that the coordinates of the virtual object boundaries are relative to that parent object. When you record a test or scripted component, OpenText Functional Testing recognizes the virtual object within the parent object and adds it as a test object in the object repository so that OpenText Functional Testing can identify the object during the run session. OpenText Functional Testing also recognizes the virtual object as a test object when you add it manually to the object repository.

To perform an operation in the Active Screen on a marked virtual object, you must first record it, so that its properties are saved in the test object description in the object repository. If you perform an operation in the Active Screen on a virtual object that has not yet been recorded, OpenText Functional Testing treats it as a standard object.

You can use virtual objects only when recording and running a test or scripted component. You cannot insert any type of checkpoint on a virtual object, or use the Object Spy to view its properties.

You can enable and disable recognition of virtual objects during recording, in the General pane of the GUI Testing tab in the Options dialog box (Tools > Options > GUI Testing tab > General node).

During a run session, make sure that the application window is the same size and in the same location as it was during recording, otherwise the coordinates of the virtual object relative to its parent object may be different, and this may affect the success of the run session.