In LoadNinja, a scenario (or load scenario) defines all the parameters for the load test run:
To work with scenarios of your project, go to the Load Test Scenarios tab of the project editor:
To view properties of some existing scenario, click this scenario in the scenario list.
Here is a sample view of scenario settings:
The Number of concurrent virtual users setting specifies the desired number of concurrent virtual users LoadNinja will simulate during the test run. The maximum number is limited by your plan. Every virtual user runs one of scripts, depending on load distribution.
|Note:||A scenario can include several scripts with multiple steps. The total number of all script steps in a scenario must not exceed 45 regardless of the plan you have.|
LoadNinja simulates every virtual user several times during the run. If some user completes their script, LoadNinja starts the next iteration of that virtual user.
Each scenario uses one of the following load types:
Duration-based means LoadNinja simulates virtual users for the specified period of time. If some virtual user completes its script, LoadNinja starts the next iteration of that user simulating the same script. The number of iterations is not limited. If the test time elapses, LoadNinja doesn’t start new iterations anymore.
For more information on load types and other parameters, see Load Configuration Settings.
For more information on scenario settings, follow these links:
Go to Projects and click your project there.
In the project editor, switch to the Scenarios tab and click Create Scenario.
This will open the scenario editor.
At the editor’s top, click to rename the scenario. Specify a new name and press Enter.
Configure scenario settings as needed.
Click Save to save the scenario and to return to Projects.
To create a scenario right after recording or editing a script:
Record a script as usual.
Click on the recorder’s toolbar to play back the script.
If the playback is successful, you will see a dialog from which you can run this script in a load test:
Click Save and run load test.
On the subsequent page, name your script and select the project you want to associate this script with, then click Save script and continue.
Next, configure the available settings:
Number of concurrent virtual users
The maximum number of concurrent virtual users (VUs) to be simulated during the run.
During the ramp-up period (if you use it), the number of concurrent virtual users will be less than this number. LoadNinja starts running the load test with 0 virtual users and adds them gradually during the ramp-up period until their amount reaches the value specified by the Virtual Users setting.
For information on how LoadNinja simulates virtual users, see Virtual users and load types.
Duration of tests (min)
|Note:||For more information, see Load Configuration Settings.|
Tip: To access other settings, click More config options. This will open the scenario editor.
Click Save and run load test to run the test based on the created scenario.
Find your scenario on the Projects > Scenarios page and click it there:
|Tip:||Use the search box to filter the scenario list. It allows searching for a specific character in a scenario name or for a specific date.|
Edit scenario settings in the scenario editor as needed.
Save the changes.
To run a load test based on a scenario, go to Projects > Scenarios, locate the needed scenario in the list and click Run on the right.
|Tip:||Use the search box to filter the scenario list. You can enter any part of the scenario name or date.|
To run a load test directly from the scenario editor, simply click Save and Run at the page’s top:
Go to Projects and click your project in the list.
In the project editor, switch to the Scenarios tab.
Find the needed scenario and select a check box on the left of it. Select the check boxes of other scenarios to be deleted.
|Tip:||Use the search box to filter the scenario list.
You can enter any part of the scenario name or of the Last Opened value.
Click Delete (this button appears above the list after you select the check box).
Confirm the deletion in the subsequent message box.