A quick guide for creating test with Record&Play

Loadium Record&Play is a feature that aims to ease and quicken your load test preparation in terms of scripting.

From installing the extension to running a test, all major points are covered in this guide in order to quickly get you to your performance tests.

Getting Started

There are 2 ways to utilize from Record&Play:

  1. You can create a script from scratch by creating HTTP Requests manually

  2. You can record your web surfing with Loadium Recorder and import it to the editor

You can go to Create Page and choose Script Builder > Record&Play to start creating a test.

Manual Creation

When you first open the Record&Play, simply press the "CREATE MANUALLY" button to start building your requests.

Loadium Recorder (Google Chrome Extension)

Allows you to record HTTP requests, URLs, their parameters, and headers while you are browsing the web.

Installing the Extension

You can find the page for installing the extension to Google Chrome here.

After installing the extension, remember to pin it from the extension manager.

Now you can easily access to Record&Play.

Editing Script

You can start editing your script after you've followed one of the processes:

  • Pressing "CREATE MANUALLY",

  • Transferring from Loadium Recorder, or

  • Importing previously recorded .json file from Loadium Recorder.

Uploading a previously recorded .json file will overwrite your current work.


Collections allow you to separate the script into smaller pieces, makes it easier to work with. Similar to Recorder UI where you can add multiple of them while recording, you can configure them here further.

You can add multiple collections if you want. For each collection, you can:

  • Add sleep which adds a delay before the next request. You can enter the delay amount (in milliseconds) as you desire.

  • Add a new request which then you can configure its details.

  • Delete the collection if you would like to.

For each request in the collection, you can:

  • Remove the request from the collection

  • Clone the request

  • Delete the request

You can also move the position of requests by gripping them from the plus "+" arrow sign, to change their order or group them in a collection.


Method Type

You can set request types as GET, POST, PUT, PATCH, DELETE, and OPTIONS.


You can add a new header or delete the existing ones.

  • To delete a header, click on the corresponding “X” button at the end of it.

  • To add a new header, click on Add Header button then enter its Key and Value parameters.


Depending on the method type, you can manage its body to send data with the request.

Query Params

You can add query parameters to your request as shown in the picture.

After Editing

At the bottom of the page, you will see 3 buttons.

  • Update JMX button allows you to save your changes done on the uploaded file.

Remember to use it frequently to prevent losing your work.

You can also download the file as JMX or JSON file.

Downloading the file without Updating JMX will download the last saved version of the file. Make sure to click on Update JMX if you want final changes included for the file.

You can also Clear Draft Changes to revert the changes done on the file.

  • Save Test button will save the test (after you give it a name in Basic Settings tab) with the .jmx file in it which can be accessed from Tests Page for future usage.

Saving the test without Updating JMX will save with the last saved version of the file. Make sure to click on Update JMX if you want final changes included for the file.

  • Clicking on Run Test will direct you to Basic Settings tab on New Test page with your .jmx file uploaded, ready to run.

Global Variables

You can define global variables to be used within requests when necessary. Utilizing this will make it easier when you need to constantly change some values within requests (for example, changing target URL from test environment to production environment).

Input Fields

  • Key: Name of the variable to be referenced for usage.

  • Value: Value stored in the variable

  • Description: Entering some self-explanatory notes about the created variable

If you don't see the answer to your question here, please reach out to us to let us know! We're always improving our documentation.

Happy Testing!

Last updated