When working with Watir and Watir-Webdriver there is a standard DOM property for an element such as name, class, id, index, scr, href etc, which is usually a straight forward way to locate an element on the page you need to get a handle of, such as select lists. But in certain cases, we come across…
Read moreWhen working with Watir and Watir-Webdriver there is a standard DOM property for an element such as name, class, id, index, scr, href etc, which is usually a straight forward way to locate an element on the page you need to get a handle of, such as select lists. But in certain cases, we come across…
Read moreWhen choosing which element locator to use in your automation tests it is important to know which locators are better to use than others. This will help you cut down on your script maintenance and strengthen your confidence that your tests are actually testing the element you intended to. We made up this fun little diagram to…
Read moreWATIR allows you to access elements based on pre-defined attributes. But there are some cases where a simple watir method cannot be used. Cases such as below: Case 1 – > There is an element that cannot be accessed using pre-defined attributes Case 2 -> There is no API for a particular HTML element Case…
Read moreHere is a method to validate if an Aria element is enabled/disabled using xpath in WATIR. The attributes that Watir provides for identifying the HTML elements on the page such as flash/Aria objects are sometimes not sufficient enough to identify elements on the page. XPath is well established and powerful query language for XML documents….
Read more