Category: <span>Selenium WebDriver</span>

Selenium Testing beyond GUI Browsers.

“Selenium automates browsers”. So goes the introductory line on Seleniumhq.org. To what extent is this a limitation? The topic of the blog provokes questions – Can we structure a Selenium-based test framework to test beyond GUI browsers? If not, at the very least, how can we improve test-effectiveness by extending an existing Selenium test-suite to work with other test-actions that do not use browsers? The first question above needs in-depth technical discussion. We focus on the second one here which can be addressed at a more conceptual level. We have an example below which illustrates how one can improve the …

A couple of words about Page Object

Often in the testing of web applications, every form on a page is described as a separate entity (object) – usually, one single form (in most cases it represents an isolated functionality) is equal to a separate class. All these objects/classes consist of web element instances (various web elements located on the related web form) and methods for interaction with the elements. Let’s imagine there is a Login form in a web application. The form may be described as: public class Login { IWebDriver driver; public Login(IWebDriver driver) { this.driver = driver; } //the class contains only one method //this …

Firebug, Firepath, and other developer tools.

Firebug, Firepath, and other developer tools. First thing should come to your mind, what are Firebug and firepath and why do I need to learn this? The answer is pretty simple, you should know that what you want to tell your selenium code to perform some action, and where? As a human, you exactly know that where you want to click on the screen or what kind of items you like to interact with. If you want to click on third menu item out of six on the screen, your mind will tell your hand or finger to move the …