Modifying Deployed Support

If you modify a deployed toolkit support set, you must reopen OpenText Functional Testing and re-run the application for the changes to take effect.

If you change the identification property definitions that specify the functionalities for which the properties are used, see the following section.

Modifying Identification Property Attributes in a Test Object Configuration File

The following attributes of the Identification Property element in the test object configuration file specify information that can be modified in the Object Identification dialog box: AssistivePropertyValue, ForAssistive, ForBaseSmartID, ForDescription, ForOptionalSmartID, and OptionalSmartIDPropertyValue. These attributes determine the lists of identification properties used for the test object. For more information, see the Test Object Schema Help.

Therefore, by default, the values of these attributes are read from the XML file only once, to prevent overwriting any changes a user makes using the Object Identification dialog box. In this way, persistence is provided for the user defined property lists.

If the user clicks the Reset Test Object button in the Object Identification dialog box, the attributes' values are reloaded from the XML.

If the XML changed since the last time it was loaded (based on the file's modification date in the system), the attributes are read from the XML. Identification properties are added to the relevant lists (and their order is adjusted if necessary) according to the values of these attributes, but no existing identification properties are removed from the lists.

To specify that the identification property lists should be completely refreshed according to the attributes defined in the XML each time OpenText Functional Testing is opened, set the DevelopmentMode attribute of the TypeInformation element in this test object configuration file to true.

Considerations When Modifying Identification Property Attributes

  • If you modify attributes of Identification Property elements in the test object configuration file, keep the DevelopmentMode attribute of the TypeInformation element set to true during the design stages of the custom toolkit support. This ensures that all of the changes you make to the file are used.

  • Before you deploy the toolkit support set for regular use, be sure to remove the DevelopmentMode attribute of the TypeInformation element (or set it to false). Otherwise, every time OpenText Functional Testing opens it will refresh the property lists based on the definitions in the test object configuration file. If OpenText Functional Testing users change the property lists using the Object Identification dialog box, their changes will be lost when they reopen OpenText Functional Testing.

  • Though existing properties are not removed from the property lists when a modified test object configuration file is read (unless the DevelopmentMode attribute is set to true), properties are added and their order is adjusted based on the definitions in the file. If OpenText Functional Testing users removed properties from the lists or modified their order using the Object Identification dialog box, those changes will be lost when a modified file is loaded.

    If you provide the custom toolkit support set to a third party, and you deliver an upgrade that includes a modified test object configuration file, consider informing the OpenText Functional Testing users about such potential changes to their identification property lists.

  • When defining a new control, you should define the ForDescription attribute as part of the test object schema. Leaving out this attribute causes your object not to be recognized during test runs (although it can be recorded).