To create a scenarioOne of the prominent features of the ALT portal is the ability to run multiple scripts concurrently via the Scenarios feature. A scenario is a container for everything that relates to a performance test. It can contain:
One or more scripts
Parameter files
Load parameters
Infrastructure agent configuration
Apica Performance Monitoring configuration
Scenarios can contain ZebraTester scripts, Selenium scripts, or URL scripts. Scenarios allow users to run tests in sequence one by one or a mix of tests at the same time. By using two scenarios, users can cover tests that gives the performance test results for each test separately and then and one that gives a complete view of the performance of all tests. This can save a lot of time on comparing tests run separately one by one. A performance test scenario can have up to 30 scripts/tests and configuration like ramp-up, duration, client-side monitoring etc.can be set individually for each script/test.
To create a Scenario, navigate to “Loadtest > Create & Run Scenario”:
...
Creating a Scenario
The basic process for creating a scenario consists of four main steps:
...
| Note |
|---|
The “Script Options” step will only appear if you click the “Script Config” button to the right of a script within the “Scripts” tab. |
Step 1: Define Scenario Settings
The general information section contains information about the scenario, which project and instance it belongs to, tags and additional information.
...
Unique scenarios can be saved via the “Save Scenario” button. The next step when creating a load test is to choose which Plans & Subscriptions to use for the test.
...
Step 2: Select scripts to include in the scenario
After choosing the desired subscription, it is time to pick the scripts to use in the scenario.
...
To configure advanced options for each script, click the “gear” icon to the right of each row:
...
Step 3: Define Script Options (optional)
| Note |
|---|
The “Script Options” step will only appear if you click the “Script Config” button to the right of a script within the “Scripts” tab. |
...
The Advanced Options section defines flow control for users and load test engine options. The Max Loops per User section defines the number of times an individually defined user will loop through the script. The Request Timeout (sec) defines the time a request will wait for a server response. It is possible to define Additional Options on a Scenario level. These additional options will apply to all scripts in the scenario. Users can define additional options exactly as they would for an individual load test. The User Input text files allow the external input of files containing User-Defined Variables.
...
Check the "Resolve DNS for Each Executed Loop " to have a new/non-cached DNS resolution per each loop execution.
Step 4: Define Test Options
Define additional test options, such as reporting, as directed in this step.
...
The schedule determines when the scenario will run. You must schedule at least one run.
...
When the schedule has been defined, the load test can be saved and initiated!. When the test is initiated, the user will be brought to the Jobs page, where they will be able to observe the Scenario as it runs.