Selenium scripts in StormRunner Load

StormRunner Load supports Selenium, an open-source load testing framework.


System requirements

StormRunner Load supports the following:

SeleniumVersion 3.2.0

Firefox 52

Chrome 56

Back to top

General requirements

  • StormRunner Load supports Selenium scripts that use the JUnit testing framework.
  • You can only run Selenium scripts on cloud based load generators and not on on-premises load generators.
  • Upload a Selenium script to StormRunner Load in .zip format.

Back to top

Upload a Selenium script to StormRunner Load

  1. Create a file that defines an execution type and entry point.

    The file is a standard Java properties file (key/value pairs). For example:

    executionThe execution engine type for the script.
    runnerThe name of the testing framework. By default, the runner is junit.
    entrypointThe entry for the testing framework. The entry point is the full class name of the Junit test entry . In the above example, it is scratch.UnitTestSample.

    A list of transaction names, separated by commas, which are displayed on the Load tests > SLA page.

    Transaction names are in the format: <package name>.<class name>.<test method name>.

  2. Create a .zip file that contains the file, your Selenium script (.jar) files and all other dependencies. The file and the *.jar files must be located in the root folder of the .zip file.

    Tip: The required JUnit and Selenium frameworks are already deployed in StormRunner Load. You do not need to include these frameworks in the .zip file.

Back to top

Transaction definition

Transactions defined in the file will appear in the Load tests > SLA page.

Transactions are defined in the JUnit test framework and transaction names are in the format: <test class full name>.<test method>.

In addition, all tests in your Selenium script will be reported as transactions. During a test run, add transactions widgets for these transactions from the gallery to the dashboard to display real time data detailing the results of your load test.

Transaction names example

Transactions are: “scratch.UnitTestSample.baseTest1” and “scratch.UnitTestSample.baseTest2”


JUnit Test java class example

package scratch;

import org.junit.Test;

public class UnitTestSample {
      public void baseTest1() {
          // The test method

      public void baseTest2() {
          // The test method

Back to top