Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Selenium Framework Design in Data-Driven Testing

You're reading from   Selenium Framework Design in Data-Driven Testing Build data-driven test frameworks using Selenium WebDriver, AppiumDriver, Java, and TestNG

Arrow left icon
Product type Paperback
Published in Jan 2018
Publisher Packt
ISBN-13 9781788473576
Length 354 pages
Edition 1st Edition
Languages
Concepts
Arrow right icon
Author (1):
Arrow left icon
Carl Cocchiaro Carl Cocchiaro
Author Profile Icon Carl Cocchiaro
Carl Cocchiaro
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. Building a Scalable Selenium Test Driver Class for Web and Mobile Applications FREE CHAPTER 2. Selenium Framework Utility Classes 3. Best Practices for Building Selenium Page Object Classes 4. Defining WebDriver and AppiumDriver Page Object Elements 5. Building a JSON Data Provider 6. Developing Data-Driven Test Classes 7. Encapsulating Data in Data-Driven Testing 8. Designing a Selenium Grid 9. Third-Party Tools and Plugins 10. Working Selenium WebDriver Framework Samples

Virtual grids


When first designing the Selenium Grid, users must decide whether they want to use physical machines or virtual machines. In this day and age of cloud computing, most users are going with a virtual grid of some sort, using either Amazon Web Services, VMware, or the Microsoft Azure Cloud Services. With mobile devices, users can test against iPhone simulators running on macOS VMs, and Android emulators running on Linux and MS-Windows VMs. To connect to the remote VM node, users can use VMware vCloud Director, Apple Remote Desktop Client, Remote Desktop Client for Windows or Linux, RealVNC, and so on.When running tests remotely on a grid, the test always starts on either a local IDE or a Jenkins Slave of some sort. The actual browser or mobile device will start on the remote node itself, not on the local VM or the Jenkins Slave. The Selenium WebDriver events will be sent from those clients to the remote hub, which will then redirect the events to the appropriate platform, start...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image