You can do more complicated things such as partial value matches, multiple custom attributes, etc. Testing by Justin Ko. Future posts will describe how to extend the locators for custom attributes. Most of the time Watir can translate the Selector Hash into a single XPath expression to quickly identify the element. The test page was a simple table:

Uploader: Maukora
Date Added: 17 November 2004
File Size: 32.28 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 44565
Price: Free* [*Free Regsitration Required]

As long as watur browser element exists, you can obtain the Xpath for interactions with Ruby, Selenium, and Watir Webdriver. The test page was a simple table:.

There are many different ways to do this. The built-in ie simplest way is to use the css or xpath locators.

Locating Elements – Watir Project

Given that css locators or css selectors are not specific to Watir, there are plenty of resources out there for handling wstir complicated scenarios — eg www. When either of these are used, they must be the only one provided in the Selector Hash.

We’ll get in touch with you ASAP. Also not XPath, but works: Testing by Justin Ko. Elements are located by creating a Selector Hash, which Watir translates into the potentially complicated information the driver needs to know to identify the element.


Fill in your details below or click an icon to log in: By continuing to use this website, you agree to their use. The highlighted element we will be taking the Xpath from.

For simplicity, we will ignore the special handling for Regexp values. Stack Overflow works best with JavaScript enabled. We are working on improving the time it takes to select the webdiver.

Post as a guest Name. The Xpath of an element is essentially a direct, precise roadmap to the specific element you are trying to select for your automated test. Antony Fuentes Artavia 2 9.

When locating nested elements elements within an element object as opposed webfriver within the browser object:. To find out more, including how to control cookies, see here: We see that each additional element method call has a significant impact, while the XPath performance is not impacted:. You can get a sense for what this looks like by checking out our sample app XPathify. By fo to use this website, you agree to their use. XPath is similar to css locators.


If your application heavily uses custom attributes, I find that it is worthwhile to extend your Watir or Watir-Webdriver gems.

You are commenting using your Facebook account.

Use of XPath in WATIR

Weberiver comments I have seen over time include: While I have seen some mentions that css locators are faster, I have not seen a practical or significant difference. I have some HTML that looks like this: Locate element via custom attribute — extending Watir Testing by Justin Ko. This post will describe briefly how to use basic css and xpath locators.

When using Watir-Classic, using XPath will always be slower. Email required Address never made public.

In the past, the Watir community has been resistive to using XPath locators. Notify me of new comments via email. In some cases, XPath actually improves performance.