Properties tab (Test Object Class designer)

This tab enables you to design the identification properties of your test object class.

Actions you can perform using Properties tab

Using Properties, you can:

Define the list of identification properties for your test object class.
Add or remove properties or select base class properties to inherit and include in the list.
Decide on the use of properties. For example: Which properties are included in test object descriptions, which can be verified in checkpoints, and used in output values, and which should be used for Smart Identification.
Optionally, define advanced options.

The information you define in this tab is stored in the XML files in your toolkit support set.

For each property that you add or inherit, JavaScript code segments are added in the relevant JavaScript file to the function that you implement to retrieve the property values from the control. (If you use the advanced options to customize the name of the implementation function or file, the code segments are not added).

Click the Implementation Code button to access the function and implement it to retrieve the property values. For details, see Implement the JavaScript retrieval function.

Note: You must also implement a JavaScript function that retrieves the values of the properties from the control. For details, see the step Implement the JavaScript retrieval function in Design test object class identification properties.

Option	Description
To access	To access the Properties tab: In the Class View, add a new test object class or double-click an existing one. The test object class designer opens. In the test object class designer, select the Properties tab. To access the advanced options, click Advanced Options.
Important information	To prevent the property grouping that you define in this tab from overwriting changes that the OpenText Functional Testing user makes in the Object Identification dialog box, clear the Development mode option in the Toolkit Support Properties designer before deploying the toolkit support set for regular use. For a more detailed explanation, see the Web Add-in Extensibility Developer Guide. Make sure to visit each tab in the test object class designer to ensure that all of the test object class details are defined correctly. An asterisk next to the name of the tab acts as a reminder that you have not yet visited this tab.
Relevant tasks	Design test object class identification properties
See also	The section on implementing support for identification properties in the Web Add-in Extensibility Developer Guide.

The Properties tab contains the following:

Property List

Displays properties that you add to the test object class, and some base class properties you can choose to inherit and include in the list.

Base class properties appear in italic font and are not supported by your test object class unless you choose to inherit them.
New or inherited properties appear in regular font and are editable.
Stored in: IdentificationProperty elements in the test object configuration XML file

This area also contains a toolbar with the following buttons:

Button	Description
	Add. Adds a new editable identification property to the test object class definition. In addition, a segment of code is added to the JavaScript function that retrieves property values from the control. Implement this segment to retrieve the value for the new property. If you rename the property, the property name used in the code segment is updated. For details on when this takes place, see When changes are applied and saved. Note: If you specified an Implementation file name or an Implementation function name in the advanced options, the code segment is not added to the JavaScript function automatically, and you must add it manually. The same is true for renaming the property. In the property name, you can enter only English letters, numeric characters, hyphens, underscores, and spaces. The first character must be a letter.
	Delete. Deletes the selected property from the test object definition in the test object configuration XML file. When you delete a property, if the section that supports this property in the JavaScript implementation function is empty, it is deleted as well. If you delete an inherited property, it appears in italic font again.
	Debug Property Retrieval. Opens the Debug Property Retrieval dialog box, enabling you to run and debug the JavaScript code that you implement to retrieve the property value from the control.
	Implementation Code. Opens the relevant JavaScript file to the JavaScript function that retrieves the property values from the control. If you select a property before clicking this button, the file opens to the relevant section within the function.
	Inherit from Base Class. Adds the selected base class property to the list of the test object class's properties. In some cases, the property is also added by default to specific property groups. The property name font changes to regular text and becomes editable. You can then add or remove the property to or from the different groups as needed. If you rename an inherited property, it appears in italic font again, and a new property is created with the new name. In addition, a segment of code is added to the JavaScript function that retrieves property values from the control, as it is when you add a new property. Implement this segment to retrieve the value for the property, if the implementation cannot be inherited from the base class. For details about inheriting base class implementation, see the section about extending an existing test object class in the Web Add-in Extensibility Developer Guide.

Property Usage Groups

Add identification properties to the different groups in this area to indicate the purposes for which the properties should be used.

To add a property from the list of properties on the left to a group on the right, select the group to open it, and then double-click the property or select it and click the button.

Base class property grouping cannot be modified unless the property is new or inherited.

Stored in: The properties' group associations are stored in the test object configuration XML file. They are indicated by attributes of the IdentificationProperty elements.

User interface elements are described below (unlabeled elements are shown in angle brackets):

UI Element	Description
	Each group has a toolbar. The toolbars all include a Delete button, to remove the selected property from the group. The groups in which the order of the properties is significant have Up and Down buttons to enable moving the selected property within the list.
Object Identification - Mandatory Group	Properties that are always learned as part of the description for test objects of this class. Note: You cannot include the same property in both Object Identification lists. Indicated by: ForDescription attribute set to `true`
Object Identification - Assistive Group	Additional properties that can be learned for a test object of the selected class to create a unique test object description. When an object is learned and assistive properties are necessary to create a unique object description, assistive properties are added to the description one at a time until there is enough information to create a unique description, according to the order you set in this group. Indicated by: ForAssistive attribute set to `true`, AssistivePropertyValue attribute set to the position of the property within the group
Smart Identification - Base Group	Properties learned as base filter properties for this test object class. The Smart Identification mechanism uses these properties to create a list of possible candidate objects. Note: You cannot include the same property in both Smart Identification lists. Indicated by: ForBaseSmartID attribute set to `true`
Smart Identification - Optional Group	Properties learned as optional filter properties for this test object class. The Smart Identification mechanism uses these properties in the specified order to narrow down the object candidate list to one object. When Smart Identification is used, a list of possible candidate objects is created according to the base filter properties. The values of the optional filter properties are then checked one by one according to the order you set, until the candidate list is narrowed down to one object. Indicated by: ForOptionalSmartID attribute set to `true`, OptionalSmartIDPropertyValue attribute set to the position of the property within the group
Checkpoints and Output Values Group	Properties available in the Checkpoint Properties and Output Value Properties dialog boxes in OpenText Functional Testing. If the check box for a property if selected, it is selected by default in the Checkpoint Properties dialog box when creating a checkpoint. Indicated by: ForVerification and, if selected, ForDefaultVerification attribute set to `true`
Object Spy Group	Indicated by: ForSpy attribute set to `true`

Advanced Options

This area enables you to set advanced options for implementing property support. If you do not define these options, OpenText Functional Testing uses default values.

User interface elements are described below:

UI Element	Description
Implementation file name	The file that contains the implementation function (optional). You cannot modify this value directly. Use the Import File button to browse to and select the relevant file. Use the Clear button to clear the edit box. The corresponding XML attribute in the toolkit configuration XML file is cleared, but the JavaScript file is not removed from the project. Default: The Default implementation file defined in the General tab Note: If you specify a name in this option, no stub is created for the function. You must create the function manually in the relevant JavaScript file. Additionally, code segments are not added or updated automatically when you add or modify properties. Stored in: Property element in the toolkit configuration XML file
	Import File. Enables you to browse to and select a JavaScript file. The file must be located in the project's `JavaScript` folder to be properly deployed. Therefore, if you select a file from another location, a local copy of the file is immediately created in the `JavaScript` folder. If the file that you import has the same name as an existing file in this folder, a period (.) and a number are appended to the imported file name (before the `.js` file extension).
Implementation function name	The name of the function that you implement to retrieve the values of the identification properties from the control. Default: get_property_value Note: If you specify a name in this option, no stub is created for the function. You must create the function manually in the relevant JavaScript file. Additionally, code segments are not added or updated automatically when you add or modify properties. If you modify the name in this option, you must update the function name in the JavaScript file as well. In this edit box, you can enter only English letters, numeric characters, hyphens, and underscores. The first character must be a letter. Stored in: Property element in the toolkit configuration XML file

UI Element

Description

Implementation file name

The file that contains the implementation function (optional).

You cannot modify this value directly.

Use the Import File button to browse to and select the relevant file.

Use the Clear button to clear the edit box.

The corresponding XML attribute in the toolkit configuration XML file is cleared, but the JavaScript file is not removed from the project.

Default: The Default implementation file defined in the General tab

Note: If you specify a name in this option, no stub is created for the function. You must create the function manually in the relevant JavaScript file. Additionally, code segments are not added or updated automatically when you add or modify properties.

Stored in: Property element in the toolkit configuration XML file

Import File. Enables you to browse to and select a JavaScript file.

The file must be located in the project's JavaScript folder to be properly deployed. Therefore, if you select a file from another location, a local copy of the file is immediately created in the JavaScript folder.

If the file that you import has the same name as an existing file in this folder, a period (.) and a number are appended to the imported file name (before the .js file extension).

Implementation function name

The name of the function that you implement to retrieve the values of the identification properties from the control.

Default: get_property_value

Note: