Book Image

Selenium Framework Design in Data-Driven Testing

By : Carl Cocchiaro
Book Image

Selenium Framework Design in Data-Driven Testing

By: Carl Cocchiaro

Overview of this book

The Selenium WebDriver 3.x Technology is an open source API available to test both Browser and Mobile applications. It is completely platform independent in that tests built for one browser or mobile device, will also work on all other browsers and mobile devices. Selenium supports all major development languages which allow it to be tied directly into the technology used to develop the applications. This guide will provide a step-by-step approach to designing and building a data-driven test framework using Selenium WebDriver, Java, and TestNG. The book starts off by introducing users to the Selenium Page Object Design Patterns and D.R.Y Approaches to Software Development. In doing so, it covers designing and building a Selenium WebDriver framework that supports both Browser and Mobile Devices. It will lead the user through a journey of architecting their own framework with a scalable driver class, Java utility classes, JSON Data Provider, Data-Driven Test Classes, and support for third party tools and plugins. Users will learn how to design and build a Selenium Grid from scratch to allow the framework to scale and support different browsers, mobile devices, versions, and platforms, and how they can leverage third party grids in the Cloud like SauceLabs. Other topics covered include designing abstract base and sub-classes, inheritance, dual-driver support, parallel testing, testing multi-branded applications, best practices for using locators, and data encapsulation. Finally, you will be presented with a sample fully-functional framework to get them up and running with the Selenium WebDriver for browser testing. By the end of the book, you will be able to design your own automation testing framework and perform data-driven testing with Selenium WebDriver.
Table of Contents (15 chapters)
Title Page
Dedication
Packt Upsell
Contributors
Preface

Standards for using static locators


The standards to use for defining locators will vary from AUT to AUT. In a perfect world, all browser and mobile pages would have a unique ID assigned to each element in the application, and users would just create a static locator using those IDs. Unfortunately, it is not a perfect world.

However, there are some common best practices that users can follow to ensure the framework is as efficient as possible.

Let's take a look at each type of locator.

Rules for using standard locators

The locator types can be divided up into three distinct categories: simple, CSS, and XPath. Let's discuss each type here.

Simple locators

Simple locators are those that have one attribute in the browser DOM or mobile page that makes them unique from other elements, and does not include any hierarchy such as a parent, child, sibling, or descendant. This includes id, name, className, tagName, linkText, and partialLinkText.

So for example, when we looked at the Google Mail login page...