Book Image

Mastering Selenium WebDriver

By : Mark Collin
Book Image

Mastering Selenium WebDriver

By: Mark Collin

Overview of this book

<p>Selenium WebDriver, also known as Selenium 2, is a UI automation tool used by software developers and QA engineers to test their web applications on different web browsers. The Selenium WebDriver API is fully object oriented compared with the deprecated Selenium RC. The WebDriver API provides multi-language support and run tests on all the most popular browsers.</p> <p>In this wide and complex World Wide Web era, this book will teach you how to tame it by gaining an in-depth understanding of the Selenium API.</p> <p>This book starts with how to solve the difficult problems that you will undoubtedly come across as you start using Selenium in an enterprise environment, followed by producing the right feedback when failing, and what the common exceptions are, explain them properly (including the root cause) and tell you how to fix them. You will also see the differences between the three available implicit waits and explicit waits, and learn to working with effective page objects.</p> <p>Moving on, the book shows you how to utilize the Advanced User Interactions API, how you can run any JavaScript you need through Selenium, and how to quickly spin up a Selenium Grid using Docker containers.</p> <p>At the end, the book will discuss the upcoming Selenium W3C specification and how it is going to affect the future of Selenium.</p>
Table of Contents (17 chapters)
Mastering Selenium WebDriver
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Baking in reliability


How can we try to enforce reliability and make sure that these changes are picked up early?

We could ask our developers to run the tests before every push, but sometimes people forget. Maybe they didn't forget, but it's a small change and it doesn't seem worth going through a full test run for something so minor. (Have you ever heard somebody say, "It's only a CSS change"?) Making sure that the tests are run and passed before every push to the centralized source code repository takes discipline.

What do we do if our team lacks discipline? What if we still keep getting failures that should have been easily caught, even after we have asked people to run the tests before they push the code to the central repository? If nothing else works we could have a discussion with the developers about enforcing this rule.

This is actually surprisingly easy; most source code management (SCM) systems support hooks. These are actions that are automatically triggered when you use a specific...