Selenium Framework Design in Data-Driven Testing

Selenium Framework Design in Data-Driven Testing

By : Carl Cocchiaro

Buy this Book

Selenium Framework Design in Data-Driven Testing

By: Carl Cocchiaro

Buy this Book

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.

Title Page

Dedication

Packt Upsell

Contributors

Preface

Free Chapter

Building a Scalable Selenium Test Driver Class for Web and Mobile Applications

Introduction

The singleton driver class

Using preferences to support browsers and platforms

Using preferences to support mobile device simulators, emulators, and real devices

Multithreading support for parallel and distributed testing

Passing optional arguments and parameters to the driver

Selenium Grid Architecture support using the RemoteWebDriver and AppiumDriver classes

Third-party grid architecture support including the Sauce Labs Test Cloud

Using property files to select browsers, devices, versions, platforms, languages, and many more

Summary

Selenium Framework Utility Classes

Introduction

Global variables

Synchronization utility classes

The JavascriptExecutor class

The TestNG Listener class

File I/O class

The image capture class

The reporter class

The JavaMail class

Summary

Best Practices for Building Selenium Page Object Classes

Introduction

Best practices for naming conventions, comments, and folder structures

Designing and building the abstract base classes for the AUT

Designing and building subclasses for feature-specific pages using inheritance techniques

Encapsulation and using getter/setter methods to retrieve objects from the page object classes

Exception handling and synchronization in page object class methods

Table classes

Summary

Defining WebDriver and AppiumDriver Page Object Elements

Introduction

Inspecting page elements on browser applications

Inspection of page elements on mobile applications

Standards for using static locators

Standards for using dynamic locators

Summary

Building a JSON Data Provider

Introduction

The TestNG Data Provider class

Extracting JSON data into Java objects

Filtering test data

JSON Data File formats

The JSONObject class

Summary

Developing Data-Driven Test Classes

Introduction

Annotating test class methods using TestNG

TestNG setup/teardown methods

Naming conventions for test methods

Using the TestNG DataProvider

Calling page object methods in test classes

Exception handling in test classes

Designing base setup classes

TestNG suite file structure

Suite parameters

Summary

Encapsulating Data in Data-Driven Testing

Introduction

Casting JSON data to Java objects

Building in positive, negative, boundary, and limit testing

Confirmation and exception property files

Property files and parsing test data on the fly

Global variables versus dynamic data

Processing JVM args

Retrieving JSON data outside of test methods

Supporting multibranded applications

Multiple driver support

Parallel testing

Summary

Designing a Selenium Grid

Introduction

Virtual grids

Selenium driver class – WebDriver versus RemoteWebDriver

Switching from local to remote driver

Selenium standalone server and client drivers

Selenium standalone server and browser driver command-line options

Appium server and mobile simulator/emulator command-line options

Selenium Grid console

Directing traffic to Selenium nodes

Third-Party Tools and Plugins

Introduction

IntelliJ IDEA Selenium plugin

TestNG results in IntelliJ and Jenkins

HTML Publisher Plugin

BrowserMob Proxy Plugin

ExtentReports Reporter API class

Sauce Labs Test Cloud services

Summary

Working Selenium WebDriver Framework Samples

Introduction

Selenium driver and DataProvider classes

Selenium utility classes

ExtentReports classes

Browser page object base and subclasses

Browser test class and data files

Browser Suite XML and Maven Pom XML files

Summary

Customer Reviews

5 star

4 star

3 star

2 star

1 star

Property files and parsing test data on the fly

In a lot of cases, the test environment data, such as username, password, servers, IP, and URL are dynamic, and change with the environment they run on. In these situations, it makes sense to use a placeholder in the test data and replace the values on the fly when the test method is run.

To do this, environment data can be stored in property files, a system property can be used to pass in the name of the file for that specific environment, and it can then be read as part of the @BeforeSuite method.

Let's take a quick look at the various parts of this equation.

Environment property files

Let's say the server URL, username, and password are dynamic and change for each test environment that the suite runs against. To handle this type of data, users can create a property file to store those values:

// sample test environment property file

server.1.url=https://myDomain.com
[email protected]
server.1.password=SuperEasyPassw0rd...

Selenium Framework Design in Data-Driven Testing

By : Carl Cocchiaro

Selenium Framework Design in Data-Driven Testing

By: Carl Cocchiaro

Overview of this book

Related Content you might be interested in

Current Title:

Selenium Framework Design in Data-Driven Testing

Selenium WebDriver Quick Start Guide

Selenium WebDriver 3 Practical Guide

Selenium Fundamentals

Property files and parsing test data on the fly

Environment property files