Hello humans!

Welcome to the documentation for Loadero, an end-to-end performance testing tool for web applications. You can launch real browsers in the cloud at scale and run Selenium web UI automation scripts in the browsers to simulate real users. Our feature-rich platform allows to run tests with thousands of participants across 12 locations without any need for the infrastructure maintenance and simulate real-world conditions actual users might experience.

Loadero API use

Learn using Loadero’s API to edit and launch your tests or access the test runs’ results without using the UI.

Test script development and examples

Read about variables, custom commands and constants to use in your test scripts. See some test script examples.

Test participants configuration

Learn about all the parameters you can set for your test participants.

Test run results

Learn what is included in the test run results reports and how to find the information you need.

Use cases described

Learn more ways to use Loadero for your performance and load tests from our blog posts.

How to Create an Automated Login Page Test and Use Multiple Credentials

Integrating Tests To Your Development Pipeline. Quickstart Guide To Loadero API

Testing Web App Performance Under Custom Network Conditions

File Upload Testing For Websites And Web Applications

How To Test Screen Sharing Feature In Web Applications

How To Set Up An Automated WebRTC Test

Frequently asked questions

How to set up test participants?

When creating a test, you will arrive at Participants tab. You can access that tab also if you click on the gear icon for a test and then choose “Edit test”. There you will be able to set the 5 primary parameters for a participant:

count - the number of copies of this participant;
browser - the specific version of a browser to use;
location - physical location of the participant;
network settings - any network speed limitation to apply;
compute unit - how powerful instance the participant has. For WebRTC tests audio and video feed parameters will also be relevant to define media inputs.

Why is my test in Pending status?

To ensure sufficient compute capacity, all tests enter a queue before they are launched. In most case the tests get launched immediately, however if the compute capacity is insufficient, the test will enter a queue before being launched and it will appear as "Pending" status. Other common test statuses are explained here.

How to make test participants follow different scenarios?

Loadero participants can be set up to follow different steps to implement more complex scenarios. You can use participant groups to separate your participants according to the action they should perform. Later in the script you can use JS, Java or Python constants to distinguish which participant is which and separate them. While all participants get the same script, the constants will be initialized with different values and control flows, such as if conditions, can take separate paths to determine steps to be executed.

What is a compute unit?

Compute unit is a value that determines the amount of machine resources that will be assigned to a test participant. A single compute unit (G1) is 50% CPU core capacity and 1GB of RAM. Variable compute units allow different applications to use Loadero efficiently - without wasting resources and at the same time having enough resources for the application to function properly. Read more about various compute units Loadero offers here.

How do assertions work?

Assertions evaluate various machine and WebRTC metrics from your test run, such as CPU, RAM usage, video FPS, audio and video bitrates and much more. All metrics are gathered throughout the test and evaluated against user-defined thresholds once the test has completed. All assertions are evaluated on a per-participant level, meaning that the same assertion can fail for one participant, but pass for another.