Identifying the Building Blocks of Web Add-in Extensibility
The sections below describe the main elements that comprise UFT One object support. These elements are the building blocks of Web Add-in Extensibility. By extending the existing support of one or more of these elements, you can develop the support you need to create meaningful and maintainable tests.
In UFT One, every object in an application is represented by a test object of a specific test object class. The test object class determines the list of identification properties and test object methods available in UFT One for this test object. The icon used to represent the test object in UFT One, for example in the Keyword View and Object Repository, is also determined by the test object class.
When UFT One learns an object, it creates a unique name for each test object on the page. A descriptive test object name enables you distinguish between test objects of the same class and makes it easier to identify them in your object repository and in tests.
By default, a test object is given the name of its test object class (appended with an index if there is more than one test object of the same class on the page). In many cases, this is not the ideal name for the custom control.
The test object name needs to be meaningful to the UFT One user, preferably using terminology that is relevant to your toolkit. UFT One displays this name in the Keyword View, in the Editor, and in the object repository.
The test object class used to represent the Web control determines the list of identification properties available for the test object. It also determines which of these identification properties are used to uniquely identify the control, which identification properties are available for checkpoints and output values (in the Checkpoint Properties and Output Value Properties dialog boxes), and which are selected by default for checkpoints. However, the actual values of the identification properties are derived from the Web control. Therefore, several Web controls that are represented by test objects from the same test object class might have different definitions for the same identification property.
The test object class used to represent the Web control determines the list of test object methods for a test object. However, the same test object method might operate differently for different Web controls represented by test objects from the same test object class. This happens because depending on the specific type of Web control, UFT One may have to perform the test object method differently.
One way to create UFT One GUI tests is by recording user operations on the application. When you start a recording session, UFT One listens for events that occur on objects in the application and writes corresponding test steps. The test object class used to represent a Web control determines which events UFT One can listen for on the Web control and what test step to record for each event that occurs.