Run Multiple Tests in Parallel with Selenium Grid

Test Cross Browser Compatibility of your website at speed and scale with Parallel Testing using Selenium Grid

Get Started free
Home Guide Selenium Grid Tutorial : How to Set It Up

Selenium Grid Tutorial : How to Set It Up

By Garima Tiwari, Community Contributor - November 19, 2024

The global automation testing market size is expected to grow from USD 28.1 billion in 2023 to USD 55.2 billion by 2028.

Automation testing has improved delivery timelines and ensured an enhanced scale of testing. From a technical perspective, this is done by performing cross-browser compatibility tests, covering a set of different browsers, devices, etc., as part of the testing process.

However, automation testing can be a time-consuming process, mainly due to the large number of browser versions, operating systems, and devices tests have to be run on.

Selenium Grid, a part of Selenium, makes this easier by offering concurrent test execution.

This Selenium Grid tutorial explores Selenium Grid — when to use it, and the steps for setting up, installation, and utilization.

Table of Contents

What is Selenium?

Selenium is a framework of automation testing tools, based on the JavaScript framework. Automated Selenium testing is greatly favoured by QAs for replicating end-user actions on websites to monitor their behaviour. It drives the interactions that occur on the target web page and could run them automatically, without requiring manual inputs.

Selenium suite comprises four components:

Let’s learn about Selenium Grid in detail.

Read More: What is Browser Automation?

What is Selenium Grid?

Selenium Grid is a smart proxy server that makes it easy to run tests in parallel on multiple machines. This is done by routing commands to remote web browser instances, where one server acts as the hub. This hub routes test commands that are in JSON format to multiple registered Grid nodes.

Hub enables simultaneous execution of tests on multiple machines, managing different browsers centrally, instead of conducting different tests for each of them. Selenium Grid makes cross browser testing easy as a single test can be carried on multiple machines and browsers, all together, making it easy to analyze and compare the results.

Why use Selenium Grid?

Selenium Grid makes automation testing more efficient. Here’s why you set up Selenium Grid to perform tests:

  • Parallel Testing: Selenium Grid lets you run multiple tests concurrently, reducing the test execution time. This is especially useful if you are handling large test suites, where running tests sequentially would consume a lot of time.
  • Centralized Test Execution: The Selenium grid unifies the control of test execution via a single hub. It handles multiple nodes (machines/virtual machines) where the tests are performed, streamlining test management, particularly in larger teams.
  • Cross-browser testing: It helps you ensure that the performance of your application is consistent across various browsers and browser combinations by enabling cross-browser testing.
  • Scalability: Selenium Grid facilitates scalability by allowing you to add more nodes to the grid and enabling parallel tests.
  • Open Source: Selenium grid is open-source and free. Additionally, the documentation is updated with every release, making it easier to install, configure, and use.

Architecture of Selenium Grid

The basic Selenium Architecture mainly consists of a hub-node model. The central hub manages multiple nodes.

  • Hub: Hub is a server that accepts access requests from the WebDriver client, routing the JSON test commands to the remote drives on nodes. It takes instructions from the client and executes them remotely on the various nodes in parallel.
  • Node: Node is a remote device that consists of a native OS and a remote WebDriver. It receives requests from the hub in the form of JSON test commands and executes them using WebDriver.

Selenium Grid Architecture

When should testers use Selenium Grid?

Testers should use Selenium Grid in the following circumstances:

  • To run tests on multiple browsers and their versions, different devices, and operating systems
  • To reduce the time that a test suite takes to complete execution

Selenium Grid improves the turnaround time of the test results. It is especially useful when the test suite is large and takes more time to run. It offers flexibility and ensures maximum test coverage within a limited time. Since the virtual infrastructure is in use, maintenance becomes easy.

Run Selenium Tests for Free

Features of Selenium Grid

Here are the features of Selenium Grid 4:

1. Architecture Support: Selenium Grid 4 supports a few additional processes that enable deployment in various ways. They are:

  • Router
  • Distributor
  • Session Map
  • New Session Queue
  • Node
  • Event Bus

2. Diverse Grid Roles: Selenium Grid can be configured via:

  • Standalone Mode
  • Classical Grid (Hub and Node)
  • Fully Distributed (Event Bus, New Session Queue, Session Map, Distributor, Router and Node)

3. Docker Support: Selenium Grid offers built-in support for docker that runs on port 2375.

4. Observability: This feature helps understand and debug the internal process since it works in a fully distributed state. Traces, metrics, and logs are the three main components that provide in-depth insights.

5. GraphQL Query Support: Being the query language for APIs, graphQL is used to query and fetch the data that the user needs. Since Selenium Grid supports, GraphQL, a simple query can bring details like current session count, node and grid updates, max session count etc.

6. Node Customization: This lets you customize and update nodes as per the test execution requirements. For example, configuring a node to perform tests on a specific browser version that the test requires.

7. External Data Store: With Selenium Grid, you can save information on the currently running sessions into an external data store.

Components of Selenium Grid 4

Here are the 6 main components of Selenium Grid 4:

  • Router: It serves as the gateway for the grid and receives external requests. Then, it guides them to the right component to be handled.
  • Distributor: Distributor manages node registration and capabilities along with assigning new session requests to the right nodes from the Session Queue. It then updates the Grid’s model with Node status.
  • Session Map: The link between Session IDs and Nodes are stored here.
  • Session Queue: Incoming session requests are held in a FIFO (first in, first out) manner.
  • Nodes: Facilitates test execution in a distributed network. Nodes with specific configurations must register with the Distributor to receive the right requests.
  • Event Bus: Enables internal communication between the grid components using messages, thus avoiding direct HTTP calls.

Components of Selenium Grid

How to setup Selenium Grid for Cross Browser Testing

Selenium Grid can be used to perform Cross Browser Testing at a scale, by running a test on different browser-device combinations simultaneously. Using parallel testing, you can ensure a consistent user experience across various browser versions and devices in a short period of time. With BrowserStack Cloud Selenium Grid you get access to 3000+ real device browser combinations for comprehensive cross browser testing.

To perform cross browser testing using Selenium Grid, follow the steps below for Selenium Grid configuration:

Step 1: Installation

Before getting started, download the Selenium Server Standalone package. This package is a jar file, which includes the Hub, WebDriver, and legacy RC that is needed to run the Grid. To get started with Selenium Grid, it is essential to have Java already installed, and set up the environment variables.

Step 2: Start Hub

Hub is the central point in the Selenium Grid that routes the JSON test commands to the nodes. It receives test requests from the client and routes them to the required nodes. To set up the Selenium Hub, open the command prompt, and navigate to the directory where the Selenium Server Standalone jar file is stored (downloaded in Step 1) using the following command.

java -jar selenium-server-standalone-<version>.jar -role hub

This will start the Hub automatically using port 4444 by default. Testers can change the default port by adding an optional parameter port, using

-host <IP | hostname>

while running the command. Testers need not specify the hostname as it can be automatically determined unless someone is using an exotic network configuration or networking with VPN. In that case, specifying the host becomes necessary.

To view the status of the hub, open a browser window and navigate to https://localhost:4444/grid/console

Step 3: Start Nodes

Whether testers are looking to running a grid with new WebDriver functionality or with the Selenium 1 RC functionality or running both of them simultaneously, testers have to use the same Selenium Server Standalone jar file, to start the nodes. To start nodes open the command prompt and navigate to the directory, where the Selenium Server Standalone jar file is stored.

Type the following command

java -jar selenium-server-standalone-<version>.jar -role node -hub https://localhost:4444/grid/register

When -role option that is provided is not specified, and it is not the hub, the default port is 5555. So, it is important to define the -role to be a node in this case.

BrowserStack Automate Banner 6

Step 4: Configure Nodes

When testers start the nodes, by default, it allows 11 browsers, i.e., 5 Firefox, 5 Chrome, and 1 Internet Explorer for concurrent use. It also allows testers to conduct a maximum of 5 concurrent tests by default.

Testers can change this and other browser settings, by configuring nodes. This can be done by passing parameters to each of the -browser switches that represent a node, based on the parameters.

As soon as the -browser parameter is used, the default browser settings shall be ignored and only the parameters that are specified in the command line shall be used.

Let us understand this with an example to set 4 Firefox version 4 nodes on a Windows machine.

 -browser browserName=firefox,version=4,maxInstances=4,platform=WINDOWS

In a case where the machine has multiple versions of Firefox,  map the location of each binary to the compatible version on the same machine.

Let us understand this by the following example where there are two versions of Firefox, namely 3.6 and 4 on the same Windows machine that have to be used at 5 and 4 instances respectively.

-browser browserName=firefox,version=3.6,firefox_binary=/home/myhomedir/firefox36/firefox,maxInstances=5,platform=WINDOWS -browser browserName=firefox,version=4,firefox_binary=/home/myhomedir/firefox4/firefox,maxInstances=4,platform=WINDOWS

This way, testers can configure the nodes as per their cross browser testing requirements, using desired combination of browsers, their versions, and operating systems.

Talk to an Expert

Step 5: Using Selenium Grid to run tests

Once the Selenium Grid setup is done by following the above 4 steps, testers can access the grid to run tests. If Selenium 1 RC nodes are being used, testers can use DefaultSelenium object and pass the same in the hub formation using the following command.

Selenium selenium = new DefaultSelenium(“localhost”, 4444, “*firefox”, “https://www.browserstack.com”);

If testers are using Remote WebDriver nodes, they must the RemoteWebDriver and DesiredCapabilities objects to define the browser, version, and platform. For this, create the target browser capabilities to run the test on:

DesiredCapabilities capability = DesiredCapabilities.firefox();

Once created, pass this set of browser capabilities into the RemoteWebDriver object:

WebDriver driver = new RemoteWebDriver(new URL("https://localhost:4444/wd/hub"), capability);

Once this is done, the hub would assign the test to a matching node, if all the requested capabilities meet. To request any specific capabilities on the grid, specify them before passing them to the WebDriver object in the following pattern:

capability.setBrowserName();
capability.setPlatform();
capability.setVersion()
capability.setCapability(,);

If these capabilities do not exist on the Grid, the code returns no match and thus the test fails to run.

Let us understand this using an example, considering a node is registered with the setting:

-browser browserName=firefox,version=4,maxInstances=4,platform=WINDOWS

Then, it is a match with the following set of capabilities defined for the test:

capability.setBrowserName(“firefox” );
capability.setPlatform(“WINDOWS”);
capability.setVersion(“4”);

It would also match with the following set of capabilities defined for the test”

capability.setBrowserName(“firefox” );
capability.setVersion(“4”);

Note that the capabilities which are not specified for the test would be ignored, such as in the above example where the platform parameter is not specified and it gets a match.

Note: You can also set Desired Capabilities by using BrowserStack Capabilities Generator

Screenshot 2020 01 30 at 7.09.24 PM

Using these steps, testers can easily set up, configure, and perform tests on Selenium Grid for concurrent execution of test suites.

Must-Read: Selenium Grid 4 Tutorial

How to perform Parallel Testing with Selenium Grid using Automate?

Using BrowserStack Automate, you can efficiently perform hundreds of parallel tests with Selenium Grid. Your test cases can be distributed across various nodes to run them concurrently.

The tool also supports cross-browser testing and real-device testing by offering access to a real-device cloud. Thus, it helps reduce the overall time taken for test execution and ensures maximum coverage across various environments.

For running parallel tests with Selenium Grid, you will have to first Sign up with BrowserStack to get your username and access_key.

Once it is done, the rest of the steps are quite simple. Please follow the help documentation.

Conclusion

Selenium Grid offers the convenience to perform concurrent testing on several browsers, browser versions, and machines. Having learned how to use Selenium Grid, testers can ensure cross-platform compatibility of their web applications with parallel testing on BrowserStack’s Cloud Selenium Grid. The Grid allows teams to instantly access to 3500+ real browsers and devices spanning different versions, manufacturers, and operating systems. real desktops, iOS, and Android devices. This makes the testing results more accurate since you can test under real user conditions, hence identifying bottlenecks and rectifying them becomes easy.

BrowserStack Automate allows you too test on 3500+ real devices and browser for a comprehensive testing experience. BrowserStack real device cloud ensure maximum test coverage by providing access to legacy and latest devices and browsers.

This would help deliver a consistent end-user experience that conforms with the continuous delivery approach using Selenium Grid.

Try BrowserStack for Free

Frequently Asked Questions

1. What is the difference between Selenium Grid and Webdriver?

Selenium Webdriver is a tool used for automation and browser interaction, while Selenium Grid is used for running parallel tests across different machines and browsers.

2. Can you use the Selenium Grid for performance testing?

No. Selenium grid cannot be used for performance testing.

Useful Resources for Automation Testing in Selenium

Methods, Classes, and Commands

Configuration

XPath

Locators and Selectors

Waits in Selenium

Frameworks in Selenium

Miscellaneous

Best Practices, Tips and Tricks

Design Patterns in Selenium: Page Object Model and Page Factory

Action Class

TestNG and Selenium

JUnit and Selenium

Use Cases

Types of Testing with Selenium

Tags
Automation Testing Selenium Selenium Webdriver

Featured Articles

Selenium 4: Understanding Key Features

Selenium Grid 4 Tutorial

Automation Tests on Real Devices & Browsers

Seamlessly Run Automation Tests on 3500+ real Devices & Browsers