Let’s run the scenario we created on the previous step.
To start a load test, in the scenario editor, click Save and Run.
Click the image to enlarge it.
A possible alternative is to run a scenario from the project’s scenario list:
Click the image to enlarge it.
Initially, on a test’s launch, you will see the timer. While this timer is on the screen, LoadNinja allocates the cloud machines needed for simulating the requested load and prepares virtual users.
After these preparatory steps, you will be able to monitor the progress of your load test in real time.
In LoadNinja, you can monitor the test results in real time and debug issues that occur during the virtual user simulation.
On the Charts tab, you can see accumulated results in graphic form:
Click the image to enlarge it.
The Statistics tab provides results of individual scripts (in our example, we have only one script; in your projects, you will see results of each script you use in your scenario):
Click the image to enlarge it.
On the VU Inspector tab, you can view desktops of remote cloud machines where virtual users are working. For each frame, you can see the virtual user ID, the name of the script it runs, and the URL the user is on. On the right, you can check the percentage of active virtual users, percentage of successful scripts, and average throughput (how many requests at a time the website handles):
Click the image to enlarge it.
On the VU Debugger tab, you can see information on errors that occur during the run. Our test will run without errors, most likely. Your tests might have errors. Here is a sample view of the VU Debugger tab:
Click the image to enlarge it.
Use the buttons on the right to dig deep into the error cause. You can —
| Command | Description |
|---|---|
 |
View the image of a web page on a cloud machine, where an error occurs. |
 |
Get information on loaded resources. |
 |
Get the HTML code of the problematic page. |
 |
Debug virtual users This will open a connection to the remote cloud machine. You will be able to run commands in the remote browser console to better understand what happened with the page. See Debug Virtual Users for details. |
When the test run finishes, the VU Inspector will hide. You will still be able to view the results on other tabs.
