Click the “Manage Tests” button to design a Test Plan. Test Plans determine how many rUsers are involved in the test, the pace at which rUsers are introduced into the test, the number of iterations each rUser will perform, and the amount of time that all rUsers will be concurrently active in the test. Most importantly, Test Plans determine which Scenarios are performed and by which rUsers.
Once a Test Plan is created it can be run immediately or you can schedule the test for execution at a future time.
Note: Be sure that rUsers have been started (showing in “Connected” column of “Real Time” page on the Controller, and sessions are visible in rUserManager on the Injector) prior to running Test Plan.
The “Manage Tests” page defaults to the “Test Plans List” view;
Create New Test Plan
Click the “Create New Test Plan” button in the menu bar. The “Test Plan” form opens;
The above image shows how the Test Plan form looks upon opening. Next, we’ll break down each section of the form and provide an image with typical sample data entered, per section:
Test Plan Name: Enter a name for the new Test Plan. Use standard alpha/numeric characters only.
Template: Attach a Template for backend monitoring (optional). Templates contain a set of system metrics configured in “Backend Monitors”.
Steady State Time: The amount of time, in minutes, that all rUsers are actively playing Scenarios. Steady State Time uses Scenario Reference Time to calculate the number of iterations per rUser. Test duration is ruled by Iterations, not Steady State Time.
Enforce SST: Select “Yes” to enforce “Steady State Time” to the Load Test. This way the load test will run for all users for a specified period.
Select “No” if you need to run the load test based on the number of iterations.
Ramp-up Time: The amount of time elapsed before all rUsers are actively playing Scenarios (rounded to the nearest minute). This field is automatically calculated based on the Test Plan details provided (field cannot be edited manually). Ramp-up time is the total time elapsed from when the first rUser starts playing a Scenario until the last rUser starts playing. In other words it is the time from the initiation of the test to the point at which the Steady State time begins.
Users / Min: The number of rUsers that begin playing Scenarios per minute. This field is automatically calculated based on the Test Plan details provided (field cannot be edited manually). This is the maximum number of rUsers injected, per minute during the Ramp-up time.
Initializing Script (Optional): Select a script that will run before any scripts in the Load Test Run.
Initializing Delay (Optional): The time, in seconds, that each rTester waits before playing the Initializing Script. A Delay value of "0" results in all rTesters begin playing the Initializing Script simultaneously. A Delay value of "5" results in each rTester begin playing the Initializing Script 5 seconds after the previous. The default value is 15 seconds.
Finalizing Script (Optional): Select a script that will run after the Injector finishes executing the script(s) in the Load Test Run.
Tip: Initialization and finalization scripts are similar to other scripts. The purpose of these scripts is to perform one-time initialization routines upon Test Plan Run starts (such as launching Web Browser, loading website, login to application, etc.) and finalization routines (properly close application, cleanup and release memory or other resources) upon Test Plan Run finishes.
Ramp-up Sequence (Optional): This option allows you to insert delays between specified numbers of rUser groups. For instance:
Start 50 users wait 20 minutes
Start 100 users waits 30 minutes
This will be interpreted as 50-20|100-30.
Note: The Graph shown in this pane provides a visual representation of the Test Plan, including ramp-up time, ramp-down time and total test run. This graphical view can also give you an idea of how many users are in the system and testing at any given time during the test.
Test Plan Details
Injector: Select the Injector on which the Scenario will play. After an Injector is selected, a new row appears below it (add as many Injectors as necessary to complete your Test Plan). Select the same Injector multiple times to play different Scenarios on the same Injector.
Scenario: Choose the Scenario to play on the selected Injector. If Scenario does not appear be sure that it has been sent from ScenarioBuilder.
rUsers: Enter the number of rUsers to play the selected Scenario on the selected Injector.
Delay: The time, in seconds, that each rUser waits before playing the Scenario. A Delay value of "0" results in all rUsers beginning simultaneously. A Delay value of "5" results in each rUser beginning 5 second after the previous.
A random Delay value can also be chosen.
Halt: Enable if you want rUsers to stop upon failure. Halted rUsers report a failure and exit the test. If disabled (unchecked), rUsers will report a failure, but will advance to their next iteration after a failed iteration – assuming the Scenario has an “On Failure” section which addresses the failure. For more about “On Failure”, please refer to this article.
+/x: Click on theicon to add another line to the Test Plan Details section.
Click on theicon to delete that line from the Test Plan Details section.
Scenario: Automatically populated (auto-filled) from the “Scenario” field in the Test Plan “Details” section.
Duration (Min.): The length of time for a Scenario to complete an iteration. This value is automatically derived from the Scenario’s “Reference Time” (established in ScenarioBuilder). This field cannot be edited.
Iterations: Value calculated from the “Steady State Time”, “Ramp-up Time”, “Users / Min”, and “Reference Time”. Iteration value may be edited (double-click and enter new value), however, note that “Steady State Time” does not adjust to reflect an override to this value.
Scenario: Automatically populated (autofilled) from the “Scenario” field in the Test Plan “Details” section.
CSV File: Automatically populated field, shows the CSV (variables) file(s) attached to each Scenario.
Access Rule: Method by which values are retrieved from the CSV file:
Fixed Row Per rUser: One row per user for all iterations. Values are retrieved in row-order.
Sequential: Values are retrieved in row-order and used repeatedly as required to complete the total number of iterations.
Random: Values are retrieved and used repeatedly, without regard for order.
Unique: Values are retrieved in row-order and used one time only.
Start Line: The row in the CSV file from which the first value is retrieved. This setting is ignored when the Random "Access Rule" is used.
Rows / User: The number of rows from the CSV file assigned to each rUser per iteration. When a Loop Action is used to call a variable mutliple times per iteration, this value must be the same as the number of times through the loop to achieve the desired result.
Rendezvous Pt.: A Rendezvous Point is a step in the Scenario where rUsers hold until a defined number of rUsers have arrived. This field is automatically populated based on Rendezvous Points defined in a Scenario. To add Rendezvous Points, edit Scenarios in ScenarioBuilder and re-send to AppLoader.
Release Policy: The number of rUsers to be released, in unison, from the Rendezvous Point. Double-click this value to edit.
Timeout: The length of time (in seconds) that each rUser will wait for the Release Policy to be met. rUsers will release either in accordance with the Release Policy or after the Timeout period elapses, whichever comes first.
Delay: The length of time each rUser waits (after the previous rUser) before continuing from the Rendezvous Point. Use to stagger the release of rUsers.
This section allows you to set up Alerts for your backend servers’ behavior. The metrics in the Template attached to the Test Plan appear in the SLA section. Here, you can assign Alerts of varying degrees of severity tied to backend metrics performance.
Double-click on the “Operator” field to reveal the list of available Operators, then double-click on the “Value” field to enter a threshold value.
Monitor: The individual backend metrics associated with the Template attached to this Test Plan.
Operator: The method by which the backend metric is compared to the threshold established on the value field.
Value: The threshold at which an Alert is triggered.
Alert Severity: Red: Error Yellow: Warning Blue: Information
Test Plan Notifications
This section allows you to set up email notification for your load test(s) status. Here, you can notify any user by email.
Put email addresses of the recipients and select/deselect the status check that you want to be notified about.
Note: You need to configure SMTP email server capability before AppLoader can send notifications. If you have not configured it, this section will not be displayed in the Test Plan form. To set SMTP Server Configuration, please refer to this article.
Save / Review / Run Test Plan
After completing all of the applicable sections of the Test Plan, click the “Save” button above the “Details” window to save your Test Plan. The following message will appear:
Click “Yes” to open the “Execution Plan” form for viewing and editing;
The Execution Plan will show you each rUser name, Host, assigned Scenario, assigned number of Iterations, Start Delay, CSV file, and Assigned CSV Rows.
Click on icon next to each rUser to view the actual value which will be pulled from the CSV file for that rUser.
Close the Execution Plan window to continue. The following message will appear:
Click “Yes” to Run your test or click “No” to exit without running. If you clicked “Yes” the following window opens. Specify a name and description for your load test and click “Submit.”
AppLoader shifts to the “Real Time” page automatically after submitting the test.