Sign In Start Free Trial

Mastering Selenium WebDriver 3.0

3.3 (3)

Mastering Selenium WebDriver 3.0

3.3 (3)

Overview of this book

The second edition of Mastering Selenium 3.0 WebDriver starts by showing you how to build your own Selenium framework with Maven. You'll then look at how you can solve the difficult problems that you will undoubtedly come across as you start using Selenium in an enterprise environment and learn how to produce the right feedback when failing. Next, you’ll explore common exceptions that you will come across as you use Selenium, the root causes of these exceptions, and how to fix them. Along the way, you’ll use Advanced User Interactions APIs, running any JavaScript you need through Selenium; and learn how to quickly spin up a Selenium Grid using Docker containers. In the concluding chapters, you‘ll work through a series of scenarios that demonstrate how to extend Selenium to work with external libraries and applications so that you can be sure you are using the right tool for the job.

Preface

Preface

Who this book is for

What this book covers

To get the most out of this book

Get in touch

Free Chapter

Creating a Fast Feedback Loop

Creating a Fast Feedback Loop

Making it easy for developers to run tests

Building our test project with Apache Maven

Running your tests in parallel

Parallel tests with TestNG

There are no silver bullets

Multiple browser support

Downloading WebDriver binaries automatically

Going headless

Summary

Producing the Right Feedback When Failing

Producing the Right Feedback When Failing

Location, location, location

Tests are living documentation

Reliability

Baking in reliability

Continuous integration is key

Extending our capabilities by using a Selenium-Grid

A picture paints a thousand words

Don't be afraid of the big bad stack trace

Summary

Exceptions Are Actually Oracles

Exceptions Are Actually Oracles

NoSuchElementException

NoSuchFrameException

NoSuchWindowException

ElementNotVisibleException

StaleElementReferenceException

InvalidElementStateException

UnsupportedCommandException

UnreachableBrowserException

SessionNotFoundException

WebDriverException – element is not clickable at point

NoAlertPresentException

Summary

The Waiting Game

The Waiting Game

Are we nearly ready yet?

I've timed it, and I know it takes 5 seconds for the page to load

So, what do we do?

I just want Selenium to do it for me

Using explicit waits

Fluent waits, the core of explicit waits

Summary

Working with Effective Page Objects

Working with Effective Page Objects

Why do you keep repeating yourself?

Starting out with page objects

Separation of concerns with page objects

Introducing the Java PageFactory class

Introducing the Query object

So, which option should I use?

Creating extensible page objects

Turning your page objects into a readable DSL

Fluent page objects

Summary

Utilizing the Advanced User Interactions API

Utilizing the Advanced User Interactions API

Getting started with the API

Using the API to solve difficult problems

Summary

JavaScript Execution with Selenium

JavaScript Execution with Selenium

Introducing the JavaScript executor

Let's not get carried away

So, what should we do with it?

A more complex example

Can I use JavaScript libraries?

Should I inject JavaScript libraries?

What about asynchronous scripts?

Building user interaction into your automation

Summary

Keeping It Real

Keeping It Real

File downloads with Selenium

You cannot track network traffic with Selenium

But I really want to track my network traffic!

Writing performance tests with Selenium

Penetration testing with Selenium

Summary

Hooking Docker into Selenium

Hooking Docker into Selenium

Introducing Docker

Spinning up Selenium-Grid with Docker

Running tests against our new Selenium-Grid

Starting up Docker containers as part of the build

Using a Docker Maven plugin

Using Docker compose

What about the negatives?

Summary

Selenium – the Future

Selenium – the Future

Machine learning — the new Holy Grail

Visual validation

Self healing tests

Having your tests written for you

Summary

Other Books You May Enjoy

Other Books You May Enjoy

Leave a review - let other readers know what you think

Appendix A: Contributing to Selenium

Appendix A: Contributing to Selenium

Selenium is amazing – how can I help make it better?

Making changes to Selenium

Appendix B: Working with JUnit

Appendix B: Working with JUnit

Switching from TestNG to JUnit

Summary

Appendix C: Introduction to Appium

Appendix C: Introduction to Appium

Creating an Appium framework

Summary

Customer Reviews

3.3 (3)

5 star

33.3%

4 star

33.3%

3 star

0

2 star

0

1 star

33.3%

Why do you keep repeating yourself?

After you have been writing automated checks for a while, you tend to see similar patterns emerging. One of the most common bad patterns that you will see is tests that interact with the same page, and the same elements on that page, in different ways.

This normally happens because more than one person has been automating scenarios in the same area, and as with all things, different people have different ways of doing things.

Let's take as an example a couple of basic HTML pages. First of all, we will have our index page. This is the page that everybody is going to see when they navigate to our website:

<!DOCTYPE html>
 <html lang="en">
 <head>
     <title>Some generic website</title>
     <link href="http://cdnjs.cloudflare.com/ajax/libs/twitter-
     bootstrap/3.3.2/css/bootstrap.min.css&quot...

Search

Your notes and bookmarks