Book Image

Selenium WebDriver Quick Start Guide

By : Pinakin Chaubal
Book Image

Selenium WebDriver Quick Start Guide

By: Pinakin Chaubal

Overview of this book

Selenium WebDriver is a platform-independent API for automating the testing of both browser and mobile applications. It is also a core technology in many other browser automation tools, APIs, and frameworks. This book will guide you through the WebDriver APIs that are used in automation tests. Chapter by chapter, we will construct the building blocks of a page object model framework as you learn about the required Java and Selenium methods and terminology. The book starts with an introduction to the same-origin policy, cross-site scripting dangers, and the Document Object Model (DOM). Moving ahead, we'll learn about XPath, which allows us to select items on a page, and how to design a customized XPath. After that, we will be creating singleton patterns and drivers. Then you will learn about synchronization and handling pop-up windows. You will see how to create a factory for browsers and understand command design patterns applicable to this area. At the end of the book, we tie all this together by creating a framework and implementing multi-browser testing with Selenium Grid.
Table of Contents (10 chapters)

Understanding the keyword driven framework

Next, we come to a very important juncture, where we come to understand what a Keyword-Driven framework is. A Keyword Driven framework is one in which keywords are written in an external file, such as .xls or xlsx . The common practice is to use the Keyword-Driven framework along with test data. Such a framework is called a Hybrid Keyword Framework.

We will have a very simple Excel document for this framework, which will be called Framework.xls, and this sheet will have two tabs, namely TestConfig and TestCases. We have already seen in Chapter 2, Understanding the Document Object Model and Creating Customized XPaths, what the TestConfig tab looks like, and we also extracted records for which the Execute column was marked as Y. Let's see what the TestCases tab looks like.

The following screenshot shows the TestCases tab:

The TestCaseID...