Selenium Testing Tools Cookbook - Second Edition - Sample Chapter
Selenium Testing Tools Cookbook - Second Edition - Sample Chapter
ee
This book is an incremental guide that addresses this need. You start off by setting up a test development
environment and learning to optimize the Selenium WebDriver API. After that, the use of design patterns
and ways to extend the Selenium WebDriver API are explained by implementing custom tasks. Next,
you will set up your own distributed environment to run parallel cross-browser tests. By the end of this book,
you will be able to solve complex testing issues on your own.
and problems
problems efficiently
real-world problems
additional coverage
$ 44.99 US
28.99 UK
P U B L I S H I N G
Unmesh Gundecha
With web technologies getting more complex and dynamic, there is an increasing need to test your web and
mobile applications on a vast number of browsers, platforms, and devices.
pl
e
P U B L I S H I N G
Sa
Unmesh Gundecha
Preface
Selenium is a set of tools used to automate browsers. It is largely used to test applications,
but its usages are not limited to testing. It can also be used to perform screen scraping and
automate repetitive tasks in a browser window. Selenium supports automation on all the major
browsers, including Firefox, Internet Explorer, Google Chrome, Safari, and Opera. Selenium
WebDriver is now a part of W3C standards and is supported by major browser vendors.
This book will help you learn advanced techniques to test web applications using the
Selenium WebDriver API and related tools. In this book, you will learn how to test web
applications effectively and efficiently with Selenium WebDriver on desktops, mobile
web browsers, and in a distributed environment.
Along with the core features of Selenium WebDriver, this book also covers design patterns
such as data-driven testing, page objects, and object maps, to design a highly maintainable
and reliable test automation framework. You will also learn how to integrate Selenium
WebDriver with ATDD/BDD, build and continuous integration tools, and perform mobile
web testing with Appium.
This book also covers techniques to extend Selenium for your specific needs. There are more
than 80 recipes that you can use to build or extend your existing test automation framework.
Preface
Chapter 3, Working with Elements, demonstrates how to use the Selenium WebDriver API to
automate interaction with various types of UI elements used in web applications, including
textboxes, buttons, dropdowns, radio buttons, checkboxes, and tables.
Chapter 4, Working with Selenium API, demonstrates how to use the Selenium WebDriver API
to build tests. We will explore the API and investigate advanced user interactions to perform
complex mouse and keyboard operations and work with various types of UI elements used in
web applications.
Chapter 5, Synchronizing Tests, demonstrates how to use the Selenium WebDriver API to
handle synchronization with implicit and explicit waits to implement robust and reliable tests.
Chapter 6, Working with Alerts, Frames and Windows, demonstrates how to handle multiple
windows, pop-ups, and alerts that are displayed during test execution.
Chapter 7, Data-Driven Testing, introduces the data-driven testing approacha widely used
methodology in test automation. Selenium WebDriver does not have built-in features to
support data-driven testing. However, we can extend the Selenium WebDriver API to support
data-driven testing. This chapter covers recipes to support data-driven testing using JUnit,
TestNG, and Apache POI to read data from spreadsheets.
Chapter 8, Using the Page Object Model, introduces the Page Object model pattern, which
is widely used for structuring Selenium WebDriver tests. This chapter provides examples
and tips on how to build testing frameworks using the Page Object model pattern.
Chapter 9, Extending Selenium, demonstrates how to extend the Selenium WebDriver API
and add features to build a scalable test automation framework. This chapter covers some of
the important recipes in extending Selenium WebDriver for various practical scenarios such
as to support custom UI controls, capture images of elements, and perform image-based
verifications.
Chapter 10, Testing HTML5 Web Applications, introduces you to using Selenium WebDriver to
test web applications using the HTML5 standard. This chapter explains how to test video and
canvas elements and the web storage API of HTML5.
Chapter 11, Behavior-Driven Development, introduces behavior-driven development with
Selenium WebDriver, using tools such as Cucumber-JVM, SpecFlow.NET for .NET, Behave
for Python, and Capybara for Ruby.
Chapter 12, Integration with Other Tools, demonstrates how to set up Selenium WebDriver
with Jenkins to run tests in Continuous Integration using Maven and ANR. This chapter also
covers recipes to use tools such as AutoIt and Sikuli to test non-web UI.
Preface
Chapter 13, Cross-Browser Testing, demonstrates how to set up a distributed test environment
with Selenium Grid for cross-browser testing. We will add nodes with various browser and
operating system combinations. We will run tests in parallel using TestNG, which helps to
reduce the time of test execution and increases test coverage. This chapter also covers how
to use cloud-based services, such as Sauce Labs and BrowserStack, for cross browser testing.
Chapter 14, Testing Applications on Mobile Browsers, introduces you to testing mobile web
applications with the Apple iOS and Android platforms using Appium. This chapter covers
recipes to configure and use Selenium WebDriver to test a mobile web application on iPhone
and Android-based devices/simulators.
Getting Started
In this chapter, we will see how to set up the Selenium WebDriver test development
environment. We will also see some basic settings to help get started with Selenium
WebDriver. You will learn the following:
Introduction
Selenium WebDriver has been widely used for automating web browsers in combination with
various tools due to its neat and clean object-oriented design. We can integrate Selenium
WebDriver with other tools to develop automated tests.
The initial sections of this chapter explore Selenium WebDriver's integration with development
and build tools such as Eclipse, Maven, and Microsoft Visual Studio. These tools provide
an easy way to develop test automation frameworks and extend the capabilities of Selenium
WebDriver API. The following recipes will explain how to set up and configure these tools
with Selenium.
Lastly, we will explore how to set up various browser drivers and initial settings for WebDriver.
Getting Started
Getting ready
You will need Eclipse and Maven to set up the test development environment. Download and
set up Maven from http://maven.apache.org/download.html. Follow the instructions
on the Maven download page (see the Installation Instructions section on the page).
Download and set up Eclipse IDE for Java Developers from https://eclipse.org/
downloads/.
The examples for this book are built in Eclipse version 4.4.2 (codenamed
Luna) for Java Developers. This comes with the Maven plugin bundled with
other packages.
Chapter 1
How to do it...
Let's configure Eclipse with Maven to develop Selenium WebDriver tests using the
following steps:
1. Launch the Eclipse IDE.
2. Create a new project by selecting File | New | Other from the Eclipse Main Menu.
3. On the New dialog, select Maven | Maven Project, as shown in the following
screenshot, and click Next:
Getting Started
4. Next, the New Maven Project dialog will be displayed. Select the Create a simple
project (skip archetype selection) checkbox and click on the Next button, as shown
in the following screenshot:
Chapter 1
6. Eclipse will create the SeleniumCookbook project with a structure (in Package
Explorer) similar to the one shown in the following screenshot:
Getting Started
7.
Select pom.xml from Package Explorer. This will open the pom.xml file in the editor
area with the Overview tab open. Select the pom.xml tab next to the Overview tab,
as shown in the following screenshot:
8. Add the WebDriver and JUnit dependencies highlighted in the following code snippet
to pom.xml in the <project> node:
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.secookbook.examples</groupId>
<artifactId>SeleniumCookbook</artifactId>
<version>0.0.1-SNAPSHOT</version>
<dependencies>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-java</artifactId>
Chapter 1
<version>2.47.1</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.12</version>
<scope>test</scope>
</dependency>
</dependencies>
</project>
You can get the latest dependency information for Selenium WebDriver
and JUnit from http://seleniumhq.org/download/maven.html
and http://maven.apache.org/plugins/maven-surefire-plugin/
examples/junit.html respectively.
TestNG is another widely used unit-testing framework
in Java World. If you want to add TestNG support to the
project instead of JUnit, you can get its Maven entry at
http://testng.org/doc/maven.html.
9. Select src/test/java in Package Explorer and right-click to show the menu. Select
New | Class, as shown in the following screenshot:
Getting Started
10. Enter com.seleniumcookbook.examples.chapter01 in the Package: textbox
and GoogleSearchTest in the Name: textbox and click on the Finish button,
as shown in the following screenshot:
Chapter 1
import
import
import
import
import
import
org.openqa.selenium.WebDriver;
org.openqa.selenium.WebElement;
org.openqa.selenium.By;
org.openqa.selenium.support.ui.ExpectedCondition;
org.openqa.selenium.support.ui.WebDriverWait;
org.junit.*;
Getting Started
});
assertEquals("Selenium testing tools cookbook - Google
Search",
driver.getTitle());
}
@After
public void tearDown() throws Exception {
// Close the browser
driver.quit();
}
}
12. To run the tests in the Maven life cycle, select the SeleniumCookbook project in
Package Explorer. Right-click on the project name and select Run As | Maven test.
Maven will execute all the tests from the project.
How it works...
Eclipse provides the ability to create Selenium WebDriver test projects easily with its Maven
plugin, taking away the pain of project configurations, directory structure, dependency
management, and so on. It also provides a powerful code editor to write the test code.
When you set up a project using Maven in Eclipse, it creates the pom.xml file, which defines
the configuration of the project and its structure. This file also contains the dependencies
needed for building, testing, and running the code. For example, the following code shows
the dependency information about Selenium WebDriver that we added in pom.xml:
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-java</artifactId>
<version>2.47.1</version>
</dependency>
10
Chapter 1
Most open source projects publish this information on their websites. In this case, you
can check http://seleniumhq.org/download/maven.html; you can also get this
information from Maven Central at http://search.maven.org/#browse. Maven will
automatically download libraries and support files mentioned for all the dependencies and
add to the project without you needing to find, download, and install these files to the project.
This saves a lot of our time and effort while managing the dependency-related tasks.
Maven also generates a standard directory structure for your code, for easier management
and maintenance. In the previous example, it created the src/test/java folder for the test
code and the src/test/resources folder to maintain resources needed for testing, such
as test data files, utilities, and so on.
Maven provides life cycle steps such as building the test code and running the test. If you are
working with the Java development team, then you might find the application code and test
code together in Maven. Here, Maven supports building the application code, then firing the
tests, and releasing the software to production.
There's more
Maven can also be used to execute the test from the command line. To run tests from the
command line, navigate to the SeleniumCookbook project folder through the command line
and type the following command:
mvn clean test
This command will traverse through all the subdirectories and run the clean command to
delete/remove earlier build files. It will then build the project and run the tests. You will see
the results at the end of execution on command line, as shown in the following screenshot:
11
Getting Started
Getting ready
You can also download and configure Ant from http://ant.apache.org/bindownload.
cgi for other OS platforms.
Windows users can download and install WinAnt on Windows. WinAnt comes with an
installer that will configure Ant through the installer. The WinAnt installer is available
at http://code.google.com/p/winant/.
This recipe uses WinAnt on the Windows OS.
You will also need Selenium WebDriver and JUnit JAR files. You can download Selenium JAR
file from http://selenium-release.storage.googleapis.com/ and JUnit JAR file
from https://github.com/junit-team/junit/wiki/Download-and-Install.
How to do it...
Let's set up the SeleniumCookbook created in the previous recipe project for Ant with the
following steps:
1. Create a lib folder and copy the JAR files for the dependencies used for this project,
that is, Selenium WebDriver and JUnit, to the lib folder, as shown in screenshot below:
12
Chapter 1
2. Create the build.xml file in the project folder with the following XML:
<?xml version="1.0" encoding="UTF-8"?>
<project name="test" default="exec" basedir=".">
<property name="src" value="./src" />
<property name="lib" value="./lib" />
<property name="bin" value="./bin" />
<property name="report" value="./report" />
<path id="test.classpath">
<pathelement location="${bin}" />
<fileset dir="${lib}">
<include name="**/*.jar" />
</fileset>
</path>
<target name="init">
<delete dir="${bin}" />
<mkdir dir="${bin}" />
</target>
<target name="compile" depends="init">
<javac source="1.8" srcdir="${src}" fork="true"
destdir="${bin}" >
<classpath>
<pathelement path="${bin}" />
<fileset dir="${lib}">
<include name="**/*.jar" />
</fileset>
</classpath>
13
Getting Started
</javac>
</target>
<target name="exec" depends="compile">
<delete dir="${report}" />
<mkdir dir="${report}" />
<mkdir dir="${report}/xml" />
<junit printsummary="yes" haltonfailure="no">
<classpath>
<pathelement location="${bin}" />
<fileset dir="${lib}">
<include name="**/*.jar" />
</fileset>
</classpath>
<test name="com.secookbook.examples.chapter1.
GoogleSearchTest"
haltonfailure="no" todir="${report}/xml"
outfile="TEST-result">
<formatter type="xml" />
</test>
</junit>
<junitreport todir="${report}">
<fileset dir="${report}/xml">
<include name="TEST*.xml" />
</fileset>
<report format="frames"
todir="${report}/html" />
</junitreport>
</target>
</project>
3. Navigate to the project directory through the command line and type the
following command:
ant
This will trigger the build process. You will see the test running. At the end, Ant will
create a report folder in the project folder. Navigate to the html subfolder in the
report folder and open the index.html file to view the results.
14
Chapter 1
How it works...
Ant needs a build.xml file with all the configurations and steps required to build the project.
We can add steps for report generation, sending e-mail notification, and so on to build.xml.
Ant provides a very dynamic framework for defining steps in the build process.
Ant also needs the necessary library/JAR files to be copied in the lib folder, which are
needed for building the project.
Ant scans for the complete set of tests in the project and executes these tests in a way similar
to Maven.
Getting ready
NuGet comes bundled with Microsoft Visual Studio 2012 onwards. However, for Microsoft
Visual Studio 2010, you will need to download and install NuGet from http://nuget.
codeplex.com.
How to do it...
Let's configure Microsoft Visual Studio 2013 to develop Selenium WebDriver tests using the
following steps:
1. Launch the Microsoft Visual Studio.
2. Create a new project by selecting File | New | Project from the main menu.
15
Getting Started
3. In the New Project dialog box, select Visual C# | Test | Unit Test Project.
Name the project as SeleniumCookbook and click on the OK button, as shown
in the following screenshot:
16
Chapter 1
5. On the SeleniumCookbook - Manage NuGet Packages dialog box, select Online and
search for the WebDriver package. The search will result in the suggestions shown
in the following screenshot:
17
Getting Started
6. Select Selenium WebDriver from the list and click on the Install button. Repeat this
step for Selenium WebDriver Support Classes. Successful installation will show a
green tick mark for both the packages, as shown in the following screenshot:
7.
9. The SeleniumCookbook project is ready for test development. You can go on adding
new tests as needed.
How it works...
NuGet Package Manager adds the external dependencies to Microsoft Visual Studio projects.
It lists all available packages and automatically downloads and configures packages to the
project. It also installs dependencies for the selected packages automatically. This saves a lot
of effort in configuring the projects initially.
18
Chapter 1
Getting ready
You will need Python or Ruby installed before installing the Selenium WebDriver client library.
Installing Python
You can download and install the latest Python version from https://www.python.org/.
In this recipe, Python 3.4 is used.
Installing Ruby
Similarly, you can download and install the latest Ruby version from https://www.rubylang.org/en/installation/. In this recipe, Ruby 2.1.3 is used.
How to do it...
Installation and setting up Selenium WebDriver with Python or Ruby is simple using
following steps.
This will get the latest version of Selenium WebDriver Python client library installed. That's it.
Let's create a simple test in Python using this installation. Create a google_search.py file
in your favorite editor or IDE and copy the following code:
import unittest
from selenium.webdriver.support import expected_conditions
from selenium import webdriver
from selenium.webdriver.support.ui import WebDriverWait
class GoogleSearch(unittest.TestCase):
19
Getting Started
def setUp(self):
self.driver = webdriver.Firefox()
self.driver.implicitly_wait(30)
self.base_url = "https://www.google.com/"
def test_google_search(self):
driver = self.driver
driver.get(self.base_url)
element = driver.find_element_by_idname("q")
element.clear()
element.send_keys("Selenium testing tools
cookbook")
element.submit()
WebDriverWait(driver, 30)\
.until(expected_conditions.title_contains("Selenium
testing tools cookbook"))
self.assertEqual(driver.title, "Selenium testing
tools cookbook - Google Search")
def tearDown(self):
self.driver.quit()
if __name__ == "__main__":
unittest.main(verbosity=2, warnings="ignore")
You can run this test using the following command line:
python google_search.py
The Python interpreter will execute the test and you will see a Firefox window being opened
and performing the search operation on Google.com. At the end of the execution you will
see the results, as shown in the following screenshot:
20
Chapter 1
This will get the latest version of Selenium WebDriver Ruby client library installed. That's it.
Let's create a simple test in Ruby using this installation. Create a google_search.rb file in
your favorite editor or IDE and copy the following code:
require "selenium-webdriver"
gem "test-unit"
require "test/unit"
class GoogleSearch < Test::Unit::TestCase
def setup
@driver = Selenium::WebDriver.for :firefox
@base_url = "https://www.google.com/"
@driver.manage.timeouts.implicit_wait = 30
end
def test_google_search
@driver.get(@base_url)
element = @driver.find_element(:name, "q")
element.clear
element.send_keys "Selenium testing tools cookbook"
element.submit()
wait = Selenium::WebDriver::Wait.new(:timeout => 10)
wait.until { @driver.title.include? "Selenium testing tools
cookbook" }
assert_equal "Selenium testing tools cookbook - Google
Search", @driver.title
end
def teardown
@driver.quit
end
end
You can run this test using the following command line:
ruby google_search.rb
21
Getting Started
Ruby interpreter will execute the test and you will see a Firefox window being opened and
performing the search operation on Google.com. At the end of the execution you will see
the results, as shown in the following screenshot:
How it works...
Selenium WebDriver is supported on various programming languages. For each supported
language, a client library or language binding is published by the Selenium developers.
These client libraries have Selenium WebDriver classes and functions that are needed
to create automation scripts.
These libraries can be installed using package installers available with the respective
languages. In this case, we used pip for Python, which connected to the PyPI (Python
Package Index) source using the Internet, downloaded the latest Selenium WebDriver
Python client library and installed with the Python directory. Similarly, Selenium WebDriver
Ruby Gem is installed using the gem utility.
Getting ready
You need to download Internet Explorer Driver Server from http://docs.seleniumhq.
org/download/. It is available in both 32bit and 64bit versions.
After downloading the IEDriver server, unzip and copy the file to the same directory in which
the scripts are stored.
22
Chapter 1
How to do it...
Let's create a test that uses Internet Explorer Driver Server with the following steps:
1. In Eclipse, create a new folder named drivers in the src/test/resources folder of
the SeleniumCookbook project. Copy the IEDriverServer.exe file to this folder,
as shown in the following screenshot:
2. Add a new test and name it as GoogleSearchTestOnIE, and add the following code:
package com.secookbook.examples.chapter01;
import
import
import
import
import
import
import
import
org.openqa.selenium.ie.InternetExplorerDriver;
org.openqa.selenium.WebDriver;
org.openqa.selenium.WebElement;
org.openqa.selenium.By;
org.openqa.selenium.remote.DesiredCapabilities;
org.openqa.selenium.support.ui.ExpectedCondition;
org.openqa.selenium.support.ui.WebDriverWait;
org.junit.*;
Getting Started
System.setProperty("webdriver.ie.driver",
"src/test/resources/drivers/IEDriverServer.exe");
DesiredCapabilities caps =
DesiredCapabilities.internetExplorer();
caps.setCapability(
InternetExplorerDriver.INTRODUCE_FLAKINESS_BY_IGNORING_
SECU
RITY_DOMAINS,
true);
// Launch Internet Explorer
driver = new InternetExplorerDriver(caps);
// Maximize the browser window
driver.manage().window().maximize();
// Navigate to Google
driver.get("http://www.google.com");
}
@Test
public void testGoogleSearch() {
// Find the text input element by its name
WebElement element = driver.findElement(By.name("q"));
// Enter something to search for
element.sendKeys("Selenium testing tools cookbook");
// Now submit the form. WebDriver will find
// the form for us from the element
element.submit();
// Google's search is rendered dynamically with
JavaScript.
// Wait for the page to load, timeout after 10 seconds
new WebDriverWait(driver, 10).until(new
ExpectedCondition<Boolean>() {
public Boolean apply(WebDriver d) {
return d.getTitle().toLowerCase()
.startsWith("selenium testing tools cookbook");
}
});
24
Chapter 1
assertEquals("Selenium testing tools cookbook - Google
Search",
driver.getTitle());
}
@After
public void tearDown() throws Exception {
// Close the browser
driver.quit();
}
}
Execute this test and you will see the Internet Explorer window being launched and all
the steps executed.
How it works...
Internet Explorer Driver Server is a stand-alone server executable that implements
WebDriver's JSON-wire protocol, which works as a glue between the test script and
Internet Explorer, as shown in following diagram:
The tests should specify the path of the IEDriverServer executable before creating the
instance of Internet Explorer. This is done by setting the webdriver.ie.driver property
as shown in following code:
System.setProperty("webdriver.ie.driver",
"src/test/resources/drivers/IEDriverServer.exe");
Internet Explorer Driver Server supports automating major IE versions on Windows XP, Vista,
Windows 7, and Windows 8 operating systems.
25
Getting Started
For more information on InternetExplorerDriver, please
visit https://code.google.com/p/selenium/wiki/
InternetExplorerDriver.
There's more
Selenium provides the ability to run tests on remote machines by using the RemoteWebDriver
class. We can configure any browser that Selenium supports for executing tests on a remote
machine. To run tests on a remote machine, we need to run the Selenium Server and the
Internet Explorer Driver Server on a remote machine and use RemoteWebDriverClass,
as shown in the following code sample:
DesiredCapabilities caps = new
DesiredCapabilities().internetExplorer();
caps.setCapability(
InternetExplorerDriver.INTRODUCE_FLAKINESS_BY_IGNORING_SECU
RITY_DOMAINS,
true);
// Connect with Remote Selenium Server with specified URL
and capabilities
driver = new RemoteWebDriver(new
URL("http://192.168.1.3:4444/hub/wd"), caps);
We can connect any browser to a remote server using the preceding method.
26
Chapter 1
Getting ready
You need to download ChromeDriver from https://sites.google.com/a/chromium.
org/chromedriver/downloads.
How to do it...
1. After downloading the ChromeDriver server, unzip and copy the file to the driver's
directory in the src/test/resources folder, as shown in the following screenshot:
org.openqa.selenium.chrome.ChromeDriver;
org.openqa.selenium.WebDriver;
org.openqa.selenium.WebElement;
org.openqa.selenium.By;
org.openqa.selenium.support.ui.ExpectedCondition;
org.openqa.selenium.support.ui.WebDriverWait;
org.junit.*;
27
Getting Started
import static org.junit.Assert.*;
public class GoogleSearchTestOnChrome {
private WebDriver driver;
@Before
public void setUp() {
System.setProperty("webdriver.chrome.driver",
"./src/test/resources/drivers/chromedriver.exe");
// Launch Chrome
driver = new ChromeDriver();
// Maximize the browser window
driver.manage().window().maximize();
// Navigate to Google
driver.get("http://www.google.com");
}
@Test
public void testGoogleSearch() {
// Find the text input element by its name
WebElement element = driver.findElement(By.name("q"));
// Enter something to search for
element.sendKeys("Selenium testing tools cookbook");
// Now submit the form. WebDriver will find
// the form for us from the element
element.submit();
// Google's search is rendered dynamically with
JavaScript.
// Wait for the page to load, timeout after 10 seconds
new WebDriverWait(driver, 10).until(new
ExpectedCondition<Boolean>() {
public Boolean apply(WebDriver d) {
return d.getTitle().toLowerCase()
.startsWith("selenium testing tools cookbook");
}
});
assertEquals("Selenium testing tools cookbook - Google
Search",
28
Chapter 1
driver.getTitle());
}
@After
public void tearDown() throws Exception {
// Close the browser
driver.quit();
}
}
Execute this test and you will see a Chrome window being launched and all the
steps executed.
How it works...
ChromeDriver is a standalone server executable that implements WebDriver's JSON-wire
protocol and works as a glue between the test script and Google Chrome, as shown in the
following diagram:
The tests should specify the path of the ChromeDriver executable before creating the instance
of Chrome. This is done by setting the webdriver.chrome.driver property as shown in
the following code:
System.setProperty("webdriver.chrome.driver","src/test/reso
urces/drivers/chromedriver.exe");
"src/test/resources/drivers/chromedriver.exe");
Getting Started
Getting ready
You need to download and install Microsoft WebDriver Server on Windows 10 from
https://www.microsoft.com/en-us/download/details.aspx?id=48212.
How to do it...
Add a new test and name it as GoogleSearchTestOnEdge.java and add the following code:
package com.secookbook.examples.chapter01;
import static org.junit.Assert.*;
import
import
import
import
import
import
import
import
import
import
org.junit.After;
org.junit.Before;
org.junit.Test;
org.openqa.selenium.By;
org.openqa.selenium.WebDriver;
org.openqa.selenium.WebElement;
org.openqa.selenium.edge.EdgeDriver;
org.openqa.selenium.edge.EdgeOptions;
org.openqa.selenium.support.ui.ExpectedCondition;
org.openqa.selenium.support.ui.WebDriverWait;
Chapter 1
@Before
public void setUp() {
System.setProperty("webdriver.edge.driver",
"C:\\Program Files (x86)\\Microsoft Web
Driver\\MicrosoftWebDriver.exe");
EdgeOptions options = new EdgeOptions();
options.setPageLoadStrategy("eager");
// Launch a new Edge instance
driver = new EdgeDriver(options);
// Navigate to Google
driver.get("http://www.google.com");
}
@Test
public void testGoogleSearch() {
// Find the text input element by its name
WebElement element = driver.findElement(By.name("q"));
// Clear the existing text value
element.clear();
// Enter something to search for
element.sendKeys("Selenium testing tools cookbook");
WebElement button = driver.findElement(By.name("btnG"));
button.click();
// Google's search is rendered dynamically with JavaScript.
// Wait for the page to load, timeout after 10 seconds
new WebDriverWait(driver, 10).until(new
ExpectedCondition<Boolean>() {
public Boolean apply(WebDriver d) {
return d.getTitle().toLowerCase()
.startsWith("selenium testing tools cookbook");
}
});
assertEquals("Selenium testing tools cookbook - Google
Search",
driver.getTitle());
}
31
Getting Started
@After
public void tearDown() throws Exception {
// Close the browser
driver.quit();
}
}
Execute this test and you will see a Microsoft Edge window being launched and all the
steps executed.
How it works...
Microsoft WebDriver Server is a standalone server executable that implements WebDriver's
JSON-wire protocol, that works as a glue between the test script and the Microsoft Edge
browser, as shown in the following diagram:
The tests should specify the path of Microsoft WebDriver Server executable before creating
the instance of Microsoft Edge. This is done by setting the webdriver.edge.driver
property as shown in the following code:
System.setProperty("webdriver.edge.driver",
"C:\\Program Files (x86)\\Microsoft Web
Driver\\MicrosoftWebDriver.exe");
32
www.PacktPub.com
Stay Connected: