Contents ▼

Recording Scripts

Recording a script from your web browser is often the easiest way to get started.

Getting the Loadster Recorder Chrome Extension

Recording is done with the help of the Loadster Recorder Chrome Extension, available in the Chrome Web Store. We’re looking at porting it to other browsers soon!

Get the Chrome extension here:

After you’ve installed the extension in your browser, expand it from the Loadster icon in the toolbar.

Toggle the switch to Enabled when you are ready to share your browser traffic with Loadster for the purposes of recording.

When you’re done recording, toggle the switch back to Disabled or uninstall the extension so that your traffic will no longer be recorded.

Recording Browser Events

To start recording, open a new or existing script and hit Record.

Loadster will open a connection to the Loadster Recorder browser extension and start listening for traffic. Open another tab and navigate to the site you want to record. Whatever you do in that browser tab will be recorded as an event and displayed in the log.

Watch the log to see what events are being recorded

If you’re not seeing traffic in the log, double-check that the Loadster Recorder browser extension is installed and enabled!

Click Stop Recording when you’re finished.

Filtering Browser Events

Many sites have a lot of 3rd party trackers and other content that you may not want in your script.

After you stop recording, uncheck any domains that you do not want included in your script.

In this example, we're excluding analytics and keeping only our own slothereum.cc traffic

When finished, click Add to Script and your traffic will be converted into steps and appended to the script.

Recording High Quality Scripts

Recording saves time, but it isn’t always perfect.

Loadster does its best to guess the relationship between pages and their resources. Typically, images and stylesheets are recorded as page resources under the pages that requested them, rather than independent steps. However, there are cases when you may need to tweak the script after recording to get it just right.

You may need to delete recorded steps that you don’t want in your script.

Always play through your script with a single v-user before running a load test, to make sure the script runs as intended!

Read more in Playing Scripts and Editing Scripts.