StaleElementReferenceException can be definitely classified as the number 1 nightmare of people who write automated tests with Selenium framework. This exception occurs when given web element with which we are trying to interact is no longer present in DOM tree. This can be caused by multiple factors...

Page Object pattern is well-known in the world of test automation. Fortunately the new version (v4) of webdriver.io test automation framework was designed with Page Object pattern in mind, so we can fully benefit from this approach. One of advanced concepts of Page Object pattern is components sharing – today we will take a closer look at this.

When I browse StackOverflow questions tagged with selenium label, a lot of them are related to the problem of clicking on page elements. It seems to be one of the most trivial tasks, but can cause a lot of problems. Very often invoking Click() action on webelement ends with exceptions (there is a wide range of them). The main reason is that element on which we try to click is not in “Interactable” state. There is a lot of different factors that can cause that situation:Element has zero dimension (width ...

A set of Selenium Grid 2, WebDriver, Gallio and Mbunit may very well prove themselves as a distributed automated testing environment and alternative for Jenkins Slave. Once properly configured environment enables to obtain information on the quality of the product throughout the SDLC. Thus, solving the problem of time testing and the diversity of environment in which those tests were run.