Create a Test Plan
Test Plans determine how many rUsers will perform 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 executed.
In order to start creating a Test Plan, login to the AppLoader Controller.
Then click “Manage Tests” button to design a Test Plan.
The “Manage Tests” page defaults to the “Test Plans List” view:
Click the “Create New Test Plan” button in the menu bar. The “Test Plan” form opens.
The image below shows how the Test Plan form looks upon opening:
Fill out the required information for each field. To accomplish this, follow the quick steps listed below:
1. Enter a name for the new Test Plan.
2. Attach a Template for backend monitoring (optional).
3. Provide a Steady State Time in minutes that all rUsers will actively play scenario. 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.
4. 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.
5. Ramp-up Time and Users/Minute will be automatically calculated based on the Test Plan details provided (these fields cannot be edited manually).
Tip: “Initializing Script”, “Initializing Delay” and “Finalizing Script” fields are optional. Please refer to the AppLoader User Guide document for more information.
6. Select the Injector. There is only one Injector that can be selected from “Injector” field in “TestPlan Details” section.
Note: As the Injector is installed on a Server, RDP Parameters for Injector (Resolution, Color Depth, etc.) will be the same as the Server.
7. Select the scenario that should be tested.
Tip: If Scenario does not appear in the drop down list on the Test Plan, most likely the Controller has not received the scenario. Check the below path:
8. Enter the number of rUsers to play the selected Scenario on the selected Injector.
Tip: Gradually ramp up to your target load. We recommend starting the test with 5-users and monitoring resources on the Injector, specifically CPU and Memory. Next try 50-users, again, ensuring that resources are sufficient.
9. As soon as you select the scenario from the “Scenario” field in the “TestPlan Details”, AppLoader automatically calculates the test duration and iterations and populates those fields on the form.
All the information about the scenario such as CSV Files, Rendezvous Points, etc. will be set automatically. Although you can change them, it is not necessary.
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;
Note: The Execution Plan shows how the Controller will assign rows from the CSV file to the rUsers and also you can view the actual parameter values that will be used by each rUser during the test.
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 or note for your load test and click “Submit”.
AppLoader shifts to the “Real Time Results” page automatically after submitting the test.