Open topic with navigation

Using the XPath search method

When new HTML controls in web applications are added to the application repository, the XPath search method is selected in the control properties by default. This search method uses an XPath query to search for an HTML control. Each control in the repository has a unique XPath, which is captured when the repository is populated. If the application changes, you can modify the XPath query for a control to make sure it is located. During playback, the XPath query is performed and QA Wizard Pro interacts with the first HTML element that matches the query. See About XPath queries.

For example, a web site with a shopping cart has a Buy button for every item available for purchase. During playback, QA Wizard Pro can distinguish between the Buy buttons because each one has a unique XPath query that specifies its exact location.

Keep the following in mind when using the XPath search method:

• Some controls require using the XPath search method and the method cannot be changed.
• If you upgrade QA Wizard Pro, some HTML controls in the application repository may use the Standard search method. If these controls are not located during playback, you can modify them to use the XPath search method. This helps improve playback accuracy by using the unique XPath for a control to specify its exact location in the HTML document hierarchy instead of the control properties and expected values criteria used by the Standard search method, which may be the same for similar HTML controls.
• You can also use XPath queries in statements to interact with HTML elements not stored in the application repository. See Using XPath queries in statements.

1. Select a control in the Application Repository pane and choose File > Properties.

The Properties dialog box opens with the Search Method tab selected.

2. Select XPath as the Search method.

3. Select the XPath query to use to find the control during playback.

• Relative XPath uses the original XPath captured for the control during recording. If the page has ID attributes, the XPath is truncated and uses the ID to locate the control.
• Full XPath uses the full hierarchical XPath captured for the control during recording.
• Custom XPath uses a custom XPath query. The value in the Relative XPath field is used by default, but you can modify it if the application changes. For example, if a control on a web page has a dynamic ID attribute that changes every time the web page refreshes, QA Wizard Pro may not find any control to perform the action on during playback. You can use a custom XPath that does not include the ID attribute to locate the control instead of the truncated XPath.

4. Click OK to save the changes.

Tip: To switch between relative and full XPath for multiple HTML controls at the same time, Ctrl+click them in the repository, right-click a selected control, and choose Search Method. See Changing the search method for multiple controls.