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

So, what do we do?


Let's face it. Figuring out whether something is ready for you to interact with is actually quite a complex process. What would you do if you were testing the site manually?

That's simple. If you were manually testing the site, you would wait for it to be ready before you started testing. The problem is, what does the term ready mean?

Well, to me, it means that the page has downloaded and the site has had a chance to render everything that looks like it needs to be rendered and it looks ready to use. Sometimes, I may start using it before it has downloaded all of the images, but I'll usually wait for the main scaffolding to be in a state that looks ready. Unless I'm looking at the network traffic, I won't know whether the AJAX requests have been resolved, but this is where my experience of what the site should look like comes in.

You may have noticed that I used the phrase looks ready a couple of times in the preceding lines. So, how do we code looks ready? Well, the problem...