Benefits of Describing Test Object Models

Implementation of a test object configuration file is optional. If you choose not to implement the test object configuration file, the test object methods defined in the .NET Custom Server DLL or control definition files will work as expected, but the functionality listed below will be missing.

Describing your custom test object methods in a test object configuration file enables the following functionality when editing GUI tests in UFT One:

  • A list of available custom test object methods in the Operations column in the Keyword view and when using the statement completion feature in the Editor.

  • A test object method selected by default in the Keyword View and Step Generator when a step is generated for a test object of this class.

  • Documentation for the custom test object methods in the Documentation column in the Keyword view.

  • Icons and context-sensitive Help (only for new test object methods added to a test object class).