How Extensibility Accelerator Tests Your Control Mapping

After you design the mapping rules and identification function that you want UFT One to use to identify the types of controls for which a specific test object class is used, you can test how this identification works. You do this in the Map to Controls Tab (Test Object Class Designer), and you do not need to have UFT One installed.

The logic that Extensibility Accelerator uses when testing the rules and deciding whether to call the identification function are the same as the logic that UFT One uses to identify the test object class to use for a custom Web control. For more details, see the section on teaching UFT One to identify the test object class to use for a custom Web control in the Micro Focus UFT One  Web Add-in Extensibility Developer Guide.

Considerations when testing your JavaScript identification function:

  • _util methods are relevant only when running in the UFT One context. Therefore, if your JavaScript identification function includes calls to _util methods, these calls are not carried out when testing the function. Instead, a message is printed in the Extensibility Accelerator Output window specifying the method call and the parameters it passed. You can make use of these messages to debug your function (Debug > Windows > Output).

  • The identification function is not called in debug mode, so you cannot use the Microsoft Visual Studio JavaScript debugging tools available in Extensibility Accelerator to debug it as it runs. If you want to use these debugging tools to debug your function, you can create a temporary test object operation that uses the identification function as its implementation function, and debug it as you would debug a test object operation.