Implementing Support for Recording

One way to add objects to the object repository and create tests in UFT is by recording. To record a test, UFT registers to listen to events on the Web elements, and, when an event occurs, UFT adds the relevant step to the test. By default, UFT uses the standard Web event configuration to determine the events to which to listen for each Web element, and the steps to record in the test when each event occurs.

If you want to customize recording on a test object class that you defined, you must specify the events that you want to record and the steps that you want UFT to add to the test when those events occur.

For each test object class on which you want to customize recording, define a Control\Record\EventListening element in the toolkit configuration file. In this element you can specify whether to use standard Web event configuration to handle events on controls represented by this test object class. In addition, you can specify whether to use standard Web event configuration to handle events that take place on those control’s children.

In addition to specifying whether UFT should use standard Web event configuration, you can specify a JavaScript function that provides more specific event registration (and optionally, the name of the file containing the function). For more information, see the Toolkit Configuration Schema Help.

In addition to the definitions in the toolkit configuration file, you write the following types of JavaScript functions:

For information on the syntax of the utility object functions, see the _util section in the API Reference. For more information on writing JavaScript functions for Web Add-in Extensibility, see Designing JavaScript functions for your toolkit support set.

You can see an example of customized recording in the sample toolkit support set for the WebExtSample environment located in %ALLUSERSPROFILE%\Documents\ExtAccTool\Samples\WebExtSample folder.

After you implement support for recording, you can record a test on controls in your environment, and verify that your toolkit support set performs correctly. For more information on testing your toolkit support set, see Testing the Toolkit Support Set During Development.