Load Testing with Selenium using the Step UI

This tutorial demonstrates how to set up a browser-based load test in the Step UI using existing Selenium tests.

Get Step SaaS for free to follow this tutorial

Illustration for Load Testing with Selenium

Note: This tutorial is designed for users who prefer setting up their tests using the Step UI. For developers, we highly recommend the code-driven approach outlined in the Load Testing with Selenium tutorial.

Prerequisites

The following tools are required to follow this tutorial:

Access to a Step cluster: Get started quickly by setting up a SaaS cluster in the Step Portal, or, if preferred, follow the Installation page to configure your own on-premise cluster.
Maven: Ensure that Apache Maven is installed on your local machine. You can download it from the official Maven website and follow the installation instructions provided here.
Google Chrome (optional): Ensure that the latest version of Google Chrome is installed on your machine. You can download it from here.
ChromeDriver (optional): Install the ChromeDriver that matches your Chrome version. You can download the correct version from the official ChromeDriver site. Make sure the ChromeDriver executable is available in your system’s PATH.

Throughout this tutorial, we will be using a sample project that automates interactions with a test environment called OpenCart, using Selenium.

1. Check out the Selenium project

Clone the sample project from GitHub:

  git clone https://github.com/exense/demo-opencart-selenium.git

Optionally, run the JUnit tests locally:

  cd demo-opencart-selenium

# If ChromeDriver is installed system-wide and added to the path:
mvn clean compile test

# Otherwise, explicitly specify the ChromeDriver path:
mvn clean compile test -Dwebdriver.chrome.driver=c:/tools/chromedriver/chromedriver.exe

Note: The test cases automatically navigate through the “Desktop” and “Components” categories of the website, as defined in the unit tests.

Take a moment to look at the sample project code – we tried to keep it as simple and straightforward as possible.

Note:

The test class (SiteTest.java) is really just a standard JUnit class, with only two changes:

First, the individual test methods carry an additional @step.handlers.javahandler.Keyword annotation. These annotations make the respective methods available as Keywords within Step.
Second, the test class itself extends the class step.handlers.javahandler.AbstractKeyword. This is a technical requirement that ensures that Step can actually use the Keyword methods.

These modifications are sufficient for the provided functionality to be used for load tests in the Step framework.

Create the Keyword Package that will be uploaded to Step:

  mvn clean package -DskipTests

After execution of this command, a JAR file named demo-opencart-selenium-0.0.0.jar is generated and located in the “target” directory of the project. This JAR file will be used in the subsequent steps of this tutorial.

2. Configure the load test in Step

Log in to the Step Portal, or sign up for free and create a Step Cluster with 10 [java, ui-automation] Agents, following this Quick setup guide.

Note: In this tutorial, we simulate 10 concurrent visits and therefore need 10 Step Agents. You can run plans with fewer Agents, but this will cause the test cases to fail if a free Agent isn’t found.

Once you’ve scaled the Agents, click Open in Step to open the Step application and carry on with the tutorial.

2.1. Upload the Keyword Package

Upload the Keyword Package built previously. The Keyword Package contains the automation steps that will be integrated in our load test.

Go to the Keywords section
Click on the Upload Package button
Select the “demo-opencart-selenium-0.0.0.jar” as the Package file
Click Save

Image showing how to upload a keyword package

2.2. Create the Plan

Create a new Plan using the TestScenario template:

Go to the Plans section
Click on the New Plan (+) button
Name the Plan, e.g. Load test OpenCart
Select “TestScenario” as the Template
Click Save and edit

2.3. Configure the load test

Note: The visual editor is the main tool for creating and editing plans in Step. We will use this to design the load test scenario.

For our load test, we will create a ThreadGroup that will repeatedly execute a task on OpenCart to simulate high loads.

In the Controls section of the Component tabs, click on the New ThreadGroup (+) button to add a ThreadGroup child to the Plan.
Hint: use the filter function in the Component tabs to easily find controls.
Select the previously defined Keyword from the Keywords section in the Component tabs.
Configure the ThreadGroup with the following parameters:

Number of Threads: 10 So the ThreadGroup runs 10 threads in parallel.
Number of iterations per thread: (empty): There should not be a limit on the number of iterations per thread;
Maximum duration (ms): 600000: The ThreadGroup should terminate after a maximum of 10 minutes (600000 ms)

Image showing how to configure a ThreadGroup to perform a load test — After following this tutorial, your Plan should look like this

Note: For more information on ThreadGroup configuration, refer to the ThreadGroup documentation.

3. Run and analyze the test

3.1. Run the load test

In Step, click Start Execution and confirm in the opened modal.

3.2. Check the status of your executions

You can continue using Step during the executions. If you wish to view detailed information about a particular execution, go to the “Executions” section in the menu and click on the individual execution of interest to reopen it.

Note: This can be done at any time, including when an execution is currently running.

Image showing execution details — Status for a successfully finished execution

3.3. Analyze the results

In the Performance tab, you can explore detailed performance metrics:

Image showing execution performance details

There you can see if the System Under Test, in our case OpenCart, can handle the amount of load we tested it with.

This tutorial serves as a starting point for those interested in performing load tests using Selenium scripts. Step enables you to reuse automation artifacts across the whole DevOps cycle, and load testing is just one aspect of it. Further learning and exploration on performance testing, synthetic monitoring and robotics can be found in other tutorials and resources.

Using Step with Grafana

This article demonstrates how to connect Grafana to data generated by Step.

Setting up system monitoring with a Step agent

This article demonstrates how to set up distributed system monitoring using Keyword executions, and analyze the results as measurements.

NET tutorials: Microsoft Office automation with Step

This tutorial demonstrates how to automate interaction with Microsoft Office applications using the Office Interop Assembly.

JUnit Plan Runner

This article provides documentation for how to integrate JUnit tests into Step.

How to monitor services availability and performance

This tutorial demonstrates how Step can be used to monitor services, availability and performance metrics.

.NET tutorials: AutoIt with Step

This tutorial demonstrates how to utilize the AutoIt C# binding to automate interactions with Windows applications.

Android Testing using Step and Appium

This article demonstrates the automation of mobile applications on Android using the Appium framework.

Browser-based automation with Step and Selenium

This article defines three Keywords which will be used in browser-based automation scenarios, using Step and Selenium, as general drivers.

Illustration for Load Testing with Cypress

Load Testing with Cypress using the Step UI - advanced

This tutorial shows you how to efficiently set up a browser-based load test using existing Cypress tests in the Step automation platform.

Adding and Configuring New Agents

In this short tutorial, we show how to quickly implement a simple browser-based load test based on Cypress scripts in Step.

Illustration for Load Testing with Playwright

Load Testing with Playwright using the Step UI

This tutorial shows you how to set up a browser-based load test using existing Playwright tests in the Step UI.

Basic Keyword Development

This article explains Keywords in Step and demonstrates how to create simple ones.

Designing functional tests

This tutorial demonstrates the design, execution, and analysis of functional tests using the web interface of Step.

Robotic Process Automation (RPA) with Selenium

This tutorial will demonstrate how to use Step and Selenium to automate various browser tasks.

Robotic Process Automation (RPA) with Cypress

This tutorial demonstrates how to use Step and Cypress to automate various browser tasks.

Synthetic Monitoring with Selenium

This tutorial demonstrates how Selenium automation tests can be turned into full synthetic monitoring using Step.

Load Testing with Cypress

In this tutorial, you'll learn how to reuse existing Cypress tests to quickly set up and run a browser-based load test using the automation as code approach.

Load Testing with Serenity BDD and Cucumber

In this tutorial, you'll learn how to reuse existing tests written with Serenity BDD and Cucumber for load testing.

Synthetic Monitoring with Cypress

This tutorial demonstrates how Cypress automation tests can be turned into full synthetic monitoring using the automation as code approach.

Load Testing with Cypress using the Step UI

In this tutorial, you'll learn how to reuse existing Cypress tests to quickly set up and run a browser-based load test using the Step UI.

Load Testing with Selenium

This tutorial demonstrates how to leverage existing Selenium tests to set up and execute browser-based load tests, following a full code-based approach.

Synthetic Monitoring with Playwright

This tutorial demonstrates how Playwright automation tests can be turned into full synthetic monitoring using Step.

Synthetic Monitoring with Cypress using the Step UI

This tutorial demonstrates how Cypress automation tests can be turned into full synthetic monitoring using the Step UI.

Robotic Process Automation (RPA) with Playwright

This tutorial will demonstrate how to use Step and Playwright to automate various browser tasks.

Distributed load testing with JMeter

This tutorial shows how to distribute JMeter tests across multiple nodes.

Load Testing with Playwright for Java

In this tutorial, you'll learn how to reuse existing Playwright tests written in Java to quickly set up and run a browser-based load test using the automation as code approach.