Last modified: 2014-10-19 17:43:56 UTC
At the moment, browsers can be driven by three APIs (from high to low level): page object, watir, selenium. Watir API is nice and Chris and I are used to it, but it is not needed. I have noticed that people new to browser testing are confused with so many options. I suggest that we no longer use watir API, but only page-object and selenium. As a first step, I will make a change in one of the repositories, so we can see if it impacts maintainability or readability of the code.
In some cases, the watir API is required. The most important case is when it is necessary to identify an element by more than one locator, which is not supported in selenium only. Looking at https://github.com/cheezy/page-object/wiki/Elements, only five access methods are marked "Watir only"
