12th May 2017

by Manoj Kumar

Selenium Grid can be a bit daunting to get up and running. Starting it is quite easy, but using it effectively can require pulling in third party tools. In this workshop we’ll cover how to run your grid effectively, using best practices culled from several large grid installations.

Overview

· Describe what the grid is intended to solve, then get into how it solves it
· Going deeper into the funnel, how is it getting its instructions, and how does it pass them to the nodes?
· What do the nodes do with these instructions, and how is it different by browser?
· What is Docker?

 

Set-up
· We’ll start with the conventional setup of hub and node servers running on the same box, for simplicity.
· Different options and flags that can be used when starting the hub/node processes
· How to simplify the start-up/shut down of hubs/nodes, what to put into a bash script, etc to help
· How do you set-up stand-alone and grid:hub-node using Docker?

 

Running
· How do you run a test in a container?
· How do you run a test against the Docker grid set-up?
· How do you look at the logs of tests running in a container?
· How do you find out which node the test was routed to?

 

Extras
· Using docker-compose to simplify docker grid setup process
· Setting up a UI for all your docker installations
· How do you scale containers?
· Overview of third-party tools: Zalenium, SeleniumGridScaler, selenium-grid-extras, just-ask

 

Requirements

Mac must be a 2010 or newer model, with Intel’s hardware support for memory management unit (MMU) virtualization; i.e., Extended Page Tables (EPT)
macOS 10.10.3 Yosemite or newer
At least 4GB of RAM

64bit Windows 10 Pro, Enterprise and Education (1511 November update, Build 10586 or later). In the future we will support more versions of Windows 10.
The Hyper-V package must be enabled. The Docker for Windows installer will enable it for you, if needed. (This requires a reboot).