Web > Advanced Pane (Options Dialog Box)

This pane enables you to modify how UFT records and runs tests and business components on Web sites.

Access this pane

To access the Advanced pane, do the following:

  1. Make sure that a GUI test is open.

  2. Select Tools > Options > GUI Testing tab > Web > Advanced node.

Back to top

Accessibility checkpoint options (tests only)

Accessibility checkpoints enable you to check that Web pages and frames conform to the W3C Web Content Accessibility Guidelines. All accessibility checkpoints in a test use the options that are selected in this dialog box during the run session.

Note: Accessibility checkpoint options are not relevant for keyword components.

Accessibility checkpoint options include the following:

Option

Description

ActiveX Check

Checks whether the page or frame contains ActiveX objects.

If so, UFT sends a warning and displays a list of the objects in the run results.

Alt Property Check

Checks that the <alt> attribute exists for all relevant objects (such as images).

If one or more objects lack the required attribute, the test fails and UFT displays a list of the objects with the missing attribute in the run results. (Selected by default.)

Applet Check

Checks whether the page or frame contains Java objects.

If so, UFT sends a warning and displays a list of the objects in the run results.

Frame Titles Check

Checks that the page and all frames in the page have titles.

If one or more frames (or the page) lack the required title, the test fails and UFT displays a list of the frames that lack titles in the run results.

Multimedia Links Check

Checks whether the page or frame contains links to multimedia objects.

If so, UFT sends a warning and displays a list of the links in the run results.

Server-side Image Check

Checks whether the page or frame contains Server-side images.

If so, UFT sends a warning and displays a list of the images in the run results.

Tables Check

Checks whether the page or frame contains tables.

If so, UFT sends a warning and displays the table format and the tags used in each cell in the run results.

Add an automatic accessibility checkpoint to each Web page while recording

Instructs UFT to automatically add an accessibility checkpoint to each Web page while recording, using the checks selected in the option above.

This option is not supported for Firefox or Chrome browsers.

Back to top

Automatic page checkpoint options (tests only)

Automatic page checkpoints enable you to check that expected and actual page properties are identical, by instructing UFT to automatically add a Page checkpoint for each Web page navigated during the recording process.

Note: Automatic page checkpoints are not supported for Firefox or Chrome browsers, and are not relevant for keyword components.

Caution: Automatic page checkpoints assume that the page content is static between record and run sessions.

If you are testing a Web page with dynamic content, using Automatic page checkpoints may cause the test to fail.

Automatic page checkpoint options include the following:

Option

Description

Broken links

Displays the number of broken links contained in the page during the run session.

If the Broken links - check only links to current host option is selected in the Web pane of the Options dialog box, this number includes only those broken links that are targeted to the current host.

For details, see Web > General Pane (Options Dialog Box).

HTML source

Checks that the expected source code is identical to the source code during the run session.

HTML tags

Checks that the expected HTML tags in the source code are identical to those in the run session.

Image source

Checks that the expected source paths of the images are identical to the sources in the run session.

Links URL

Checks that the expected URL addresses for the links are identical to the URL addresses in the source code during the run session.

Load time

Checks that the expected time it takes for the page to load during the run session is less than or equal to the amount of time it took during the record session PLUS the amount of time specified in the Add seconds to page load time option.

For details, see Web > General Pane (Options Dialog Box).

Number of images

Checks that the expected number of images is identical to the number displayed in the run session.

Number of links

Checks that the expected number of links is identical to the number displayed in the run session.

Create a checkpoint for each Web page while recording

Instructs UFT to automatically add a Page checkpoint for each Web page navigated during the recording process.

Ignore automatic checkpoints while running tests

Instructs UFT to ignore the automatically added Page checkpoints while running your test.

Back to top

Recording options

The following options enable you to set preferences for recording Web objects.

Option

Description

Enable Web support for Microsoft Windows Explorer

When selected, UFT treats relevant objects in Microsoft Windows Explorer as Web objects. When cleared, UFT does not record events on Web pages displayed in Microsoft Windows Explorer.

After modifying this setting, for the change to take effect, you must close all instances of Microsoft Windows Explorer (confirm that all explorer.exe processes are closed in the Windows Task Manager or restart the computer) and then restart UFT.

Record coordinates

Records the actual coordinates relative to the object for each operation.

Record MouseDown and MouseUp as Click

Records a Click method for mouseup and mousedown events.

For Web, UFT records RightClick and MiddleClick methods for most Web objects. Therefore, this option is relevant only for clicks made using the left mouse button.

Record Navigate for all navigation operations

Records a Navigate statement each time a Frame URL changes.

This option is not supported for Firefox or Chrome browsers.

Use standard Windows mouse events

Instructs UFT to use standard Windows mouse events instead of browser events for the following events:

  • OnClick
  • OnMouseDown
  • OnMouseUp

Note: Use this option only if the events are not properly recorded using browser events.

For Web, UFT records RightClick and MiddleClick methods for most Web objects. Therefore, this option is relevant only for clicks made using the left mouse button.

This option is available only for Internet Explorer.

Tip: If UFT does not record Web events in the way you need, configure the events you want to record for each type of Web object.

For example, to record an event such as a mouse-over that opens a sub-menu, you may need to modify your Web event configuration to recognize such events.

For details, see Event recording configuration.

Back to top

Run options

The following options enable you to set preferences for working with Web objects during a run session.

Option

Description

Browser cleanup

Closes all open browsers after the test run.

When this option is selected, all currently open browsers are closed when the current test ends, regardless of whether the browsers were opened before or after UFT was opened.

Run only click

Determines whether a Click operation is run on the application by sending MouseDown, MouseUp, and Click events, or by sending only a Click event. This option is relevant only for Click operations when Event is selected for the 'Replay type' option. It is relevant only for left-button mouse clicks.

Replay type

Configures how to run mouse operations according to the selected option:

  • Event. Runs mouse operations using browser events.
  • Mouse. Runs mouse operations using the mouse, and keyboard operations using the keyboard.
Run using source index

Instructs UFT to learn and store the source index value when learning Web test objects, and to use that value during a run session to improve performance. During run sessions, UFT uses the learned source index value to return the relevant DOM element from the application and then verifies that this object matches the test object description. This operation is faster than searching the entire DOM for objects that match the test object description.

If the returned object does not match the description, the source index is ignored and UFT attempts to identify the object using the standard object identification process.

The source index is also ignored during a run session in the following scenarios:

  • The description for a test object includes the XPath or css identifier. For details, see Web object identifiers.
  • If you manually define an Index ordinal identifier for the test object.
  • The run session is performed using a browser other than Internet Explorer.

This option is not supported for Firefox or Chrome browsers.

Resize browser on run if resized during a recording session

If you select this option and then resize the browser during a recording session, UFT resizes the browser to this size when the first time you run the recorded steps. At the end of a run session, the browser returns to its default size. We recommend that you select this option if your test performs drag and drop operations.

  • To use this option, select the Open the following browser option in the Record and Run Settings dialog box before recording.
  • When this option is cleared, UFT does not change the browser size when a run session begins. If you run your steps with this option cleared, and the select this option again, UFT opens the browser to the same size as the previous run session, regardless of any resizing information you provided when recording the steps.
Learn and run using automatic XPath identifiers (Web Add-in only)

Generates and stores an XPath value when learning Web test objects, and uses that value during a run session to improve object identification reliability. During the run session, UFT uses the learned XPath value to return the DOM element from the application and verifies that this object matches the test object description. If it does not, the learned XPath is ignored.

Additionally, if the description for a test object includes the XPath or CSS identifier, or if the Run using source index option is selected, then this option is ignored for that object. For details, see Web object identifiers.

Back to top