The basic steps for creating a scenario consists of five steps:
Select a subscription
Define general information
Select scripts to use in the scenario
Configure Performance Agents
Configure Scenario Options
Step 1: Select a Subscription
The first step when creating a load test is to choose which Plans & Subscriptions to use for the test.
View
Step 2: Define General Information
The general information section contains information about the scenario, which project it and instance it belongs to, tags and additional information.
The Saved scenarios button lets you choose a Saved Scenario.
Step 3: Select Desired Scripts
After choosing the desired subscription, it is time to pick the scripts to use in the scenario.
Projection
As you select scripts and configure them, a projection is shown below the configuration.
Step 4: Configure Performance Agents
When you have set up the script sequence, you can configure performance agents:
Schedule
The schedule determines when the scenario will run. You must schedule at least one run.
Step 5: Configure Scenario Options
Advanced Options: Flow control for users and load test engine options.
Max Loops per User
Unlimited (Default)
1-20 in increments of 1
20-100 in increments of 5
100-200 in increments of 10
Request Timeout (sec)
60 (Default)
1-20 in increments of 1
20-100 in increments of 5
100-200 in increments of 10
Additional Options
[TBD]
User Input text files: Allows the external input of files containing User-Defined Variables.
(Required) Locations: Select the Load Generation location, or Cluster of Load Generation locations before running the test.
Select from the map or use the dropdown box for a list of all locations/clusters.
Note that you can select a set of locations and then Save them as a Cluster for ease of re-use.
When a bold Red X is next to a selected cluster, this is the option to delete the cluster
After the confirmation dialog
Client options: Load test client behavior and settings.
Clientside Monitoring: Basic service monitoring through a single endpoint (URL), or a monitoring script (Selenium IDE).
DNS: Domain name lookup behavior and DNS servers.
Allows (1) a DNS Hosts File(s) to provide a TXT file as input/translation or (2) a specific DNS Server to the load test execution.
Check the "Resolve DNS for Each Executed Loop " to have a new/non-cached DNS resolution per each loop execution.
When the performance agents have been configured, the load test can be saved and initiated!