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 moreSikuli Best Practices If you have been struggling to build complex interactive UI application tests with DOM based technologies like Watir or Selenium. You have come to the right blog, because project Sikuli is transforming the test case creation process by adding visual image verification to the arsenal of test automation. We have been…
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 moreOur Customers typically have 4-7 “lower” environments where the underlying application is deployed and tested, multiple times by multiple teams before making it into “production”. One of the big benefits of using Awetest is the ability to create and test new environments on the fly using existing scripts. When an automation script is written, it…
Read moreI have been working on Ruby and Watir technologies for a while now. While enjoying the versatility of Watir (as evident from Željko Filipin’s Watir solution for playing pacman, http://zeljkofilipin.com/2010/05/29/play-google-pacman-with-watir/) – I realized that there are certain scenarios in which we do not have direct method for accomplishing a task. For example, when we have…
Read more
WATIR 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 moreWhen doing automated testing, it’s common to run into a basic authentication window before you can access the application. WATIR can’t handle these authentication windows very well because it’s basically a modal popup with no associated DOM. That’s where AutoIT can be used to handle these authentication windows. You can use AutoIT to send basic…
Read moreModal dialogs are pop-ups that need attention before the user can go back to their testing window. Modal dialogs are difficult to automate using only Ruby and Watir because you can’t access the html source code of a modal dialog. Since AutoIT does not require any source code to operate, it is a viable tool…
Read moreAnother useful feature of AutoIt is its ability to manipulate the mouse directly. It makes it possible to grab a window or browser box and move it about or to grab a window handle and move that to re-size it. But before you can move something you have to find out where your target is…
Read moreAutoIT is a powerful tool to use in conjunction with Ruby/Watir because it allows you to manipulate windows and simulate actions without requiring the use of the source code. This is especially useful for pop-ups such as modal dialogs or file downloads.
Read more