Known issues - Web Add-in

This section contains general troubleshooting and limitation information about working with the Web Add-in.

Object Identification

  • Zooming in or out on your web page, or using Windows display settings other than 100%, may cause UFT to behave unexpectedly. For example, you may experience differences when highlighting or recognizing objects.

  • If you open UFT with the Siebel Add-in loaded, the Web Add-in does not appear in the Object Identification dialog box.

    Workaround: Change the value of the HKEY_CURRENT_USER\Software\Mercury Interactive\QuickTest Professional\MicTest\Packages\SiebelPackage\Settings\AllowWebToConfig registry key value to 1.

  • If your application objects do not implement the aria-selected attribute in the application's controls, certain description properties, such as the selected, items count, selected items, selection, and value return empty values.

  • If the child items in a WebTree object are generated dynamically (for example, they are not visible or present in the application until the parent node is expanded), UFT may not be able to select the items in the tree automatically using the .Select method. 

    Workaround: Manually add steps to make the nodes visible or expand tree nodes to create the object in the application.

Back to top


  • Autocomplete is not supported during recording sessions. When recording on an autocomplete control, enter the full string instead of selecting the suggestion provided by the control. The step is recorded in the same way as other (non-autocomplete) controls.

    Workaround: You can disable the AutoComplete feature in Microsoft Internet Explorer by selecting Tools > Internet Options > Advanced and deselecting the Use inline AutoComplete under the Browsing options.

  • If a WebTree object contains separate objects inside the tree (such as a checkbox object), these child objects are not recorded.

    Workaround: Do one of the following:

    • Spy on the child object to get the relative Xpath value of the tree item. Then, add a WebTree.Select method, with the Xpath value you retrieved from the spy for the XPath argument of the .Select method.

    • Add the object into the object repository and manually add it to the test or component.

Back to top

Recognition of WebTable Test Objects

  • By default, when using the UFT Web Add-in, UFT recognizes any HTML table as a WebTable test object.

    However, in QuickTest 9.5 or 10.00, the default behavior was to ignore HTML tables with one row and one column during Object Spy, learn, and record sessions.

    In specific situations, this changed default behavior may result in differences when learning new test objects or when running steps containing Web test objects that were learned in QuickTest 9.5 or 10.00. For example, the ChildObjects method may return a different value for parent objects that contain Web tables.

    If necessary, you can revert to the previous behavior by enabling (and optionally modifying) abstract table support.

    Abstract tables are defined in a built-in Web Add-in Extensibility toolkit support set called HPInternal. By default, this toolkit support set is not loaded.

    1. Open <UFT installation folder>\dat\Extensibility\Web\Toolkits\HPInternal\loadalways.ind

    2. Change the single line in the file to: load=true

    To modify which types of tables UFT treats as an abstract table:

    Edit the IsHPAbstractTable JavaScript located in: <UFT installation folder>\dat\Extensibility\Web\Toolkits\HPInternal\HPAbstractTable.js.

    The sample IsHPAbstractTable JavaScript function below causes UFT to treat Web table elements containing one row and one column as abstract tables:

    function IsHPAbstractTable()
    	// Treat all tables with only one cell as abstract tables
    	if ( _elem.rows.length == 1 && _elem.rows[0].cells.length == 1 )
    		return true;
    	return false;

    To instruct UFT to ignore additional types of Web table elements, modify the IsHPAbstractTable JavaScript function to return true for those types based on their HTML properties or other information. (Use the token _elem to represent the Web element UFT is currently handling.)

    Caution: HPAbstractTable.js affects the way UFT identifies Web objects and can cause problems if modified incorrectly. Edit this file only if you are an experienced JavaScript programmer and are familiar with the implementation of your Web controls. Make sure to create a backup copy of the file before making changes.

  • If you are recording actions on objects embedded in a Web table, these actions may not be recorded properly. Readjust your test after recording as necessary.

Chromium Embedded Framework

Non-supported functionalities

  • Object Spy

  • Navigate and Learn

  • Drag and Drop

  • Active Screen

  • Web options (Tools > Options > GUI Testing tab > Web node)

  • Recording on multiple tabs or windows

  • Low-level recording


When recording, a page navigation script may display after a page is fully loaded.

This may lead to errors when recording.

To avoid errors in your script, wait until the navigation step is recorded before continuing.


Only standard, bitmap, and text/text area checkpoints are supported.

Unsupported test objects and methods

  • Browser dialog boxes (like Alert, Confirm, Prompt)

  • Browser methods

  • Modal or modaless dialog boxes

  • * chrome://* pages

  • * about://* pages

  • WebFile test objects

  • ViewLink test objects

  • WebXML test objects

Localized versions

When working in localized versions of UFT, connecting to an application that includes Chromium Embedded Framework objects via the localhost may have errors.

In such cases, use the IP address instead.

Ending processes manually

You may need to end the WebDriverHost.exe and chromedriver.exe processes manually in the following situations:

  • If UFT was connected to an incorrect port

  • If the CEF application was not closed correctly.

In such cases, you must end these processes manually to avoid unexpected behavior when working with the CEF application.

Using Web applications with PhantomJS

Recording Recording on PhantomJS toolkits is not supported.
Unsupported contols

The following controls are not supported:

  • Browser dialogs, such as Alert, confirmation, or prompt dialogs

  • about://* pages

  • iFrame or cross-domain frame objects

  • Objects created with Web 2.0 technologies (ASAP .NET AJAX, Dojo, Google Web Tools, jQueryUI, SiebelOpenUI and YahooUI)

Unsupported Functionalities
  • Recording

  • Object Spy

  • Highlight in Application

  • Navigate and Learn

  • Add Objects to Local button in the Object Spy

  • Drag and Drop functionalities

Test Objects and Methods

The following objects are not supported

  • WebButton created by the role=button property

  • WebList created by the role=list property

  • WebMenu

  • WebTable created by the role=table or role=grid property

  • WebTabStrip

  • WebTree

  • Link object created by the role=link property

  • WebFile

  • WebVideo

  • WebAudio

  • ViewLink

The following test object methods are not supported:

  • Browser.ClearCache

  • Browser.DeleteCookies

  • Browser.Home

  • Browser.Object

  • Browser.IsSiblingTab

  • Browser.Stop

  • Browser.HandleDialog


When running tests with the CaptureBitmap method with a large page source, a general run error is thrown.

Running tests Maintenance Run Mode is not supported.

See also: