This will give you a good sense of how to build a scenario and run a test.
Evaluation using just one user can be done with all components on your PC. This will give you a good sense of how to build a scenario and run a test.
After this is done, you will have the option to increase load either with servers (with multiple robots each), or running multiple PCs with one robot on each.
Please note that when you are ready to ramp up the test on servers, you may need to adjust your scenario (retake images) to be compatible with the server environment, as images may be rendered differently on a server than on your PC.
***If you wish to go directly to set up a 5 user test on a server, click here to go to EVAL OPTION NUMBER 2: 5 user test on a server:
A brief overview of the product
AppLoader uses robots called rUsers to simulate multiple users accessing your application from the front-end; exactly how it will be accessed in production.
AppLoader uses a Distributed Architecture so that you can simulate load from different locations and scale easily. There is no coding necessary to set up your scripts.
The Controller: Where you manage and monitor tests:
1. Distribute the scripts to all the robots on the Injectors
2. Create test plans
3. Schedule tests
4. Create and view load test reports
Robots (rUsers): Each rUser simulates one real user. These are located on the Injectors and run the scenarios from their own desktops at the direction of the Injector.
Injector: This is the component that controls the rUsers, runs tests, and sends results back to the Controller. Contains the rUserManager that creates a session for each rUser.
Each injector is located on its own machine, manages the robots on that server, and acts independently of other injectors. (Usually, an injector can handle up to 100 rUsers.)
ScenarioBuilder: Code-free engine for creating scenarios/scripts of business processes.
Install the Controller, Injector, and ScenarioBuilder on the same PC.
Make sure the PC has access to the application you need to test.
CREATE and VALIDATE YOUR SCENARIO
Before you start your scenario, know your application
Before you start recording and building the script, go through the process on your application manually and understand what steps you will need the robots to do. (Example: Log into an application, look up a record, and log out).
Build your Scenario:
- Open Scenario Builder.
- Enter a name for your project.
- Build a scenario by clicking the “New” button on the top left to create your Scenario.
- Click on the "Start Recording" option
Now begin going through the process on your application. ScenarioBuilder will be listing the steps in a script as you go.
When you are done, click on "Stop" button, ScenarioBuilder will go back to the main window. You will see the recorded steps as individual actions.
Afterward, you can edit the script, break it into subscripts, update any actions or images, add transactions, etc.
(Later, you can divide and organize your scripts to make them more sophisticated and easier to edit, loop certain parts, etc. To learn more, see this article.)
Play and Validate your Scenario:
Once the scenario is built, run it by clicking on the “Play” button. Run multiple iterations to make sure that the scenario was finished correctly and everything is ready for the start of the next iteration.
If the scenario runs to the end without any errors and runs multiple times without errors, it is valid to use in a load test. If the scenario aborts on an error, debug the scenario with viewing the failure screenshot and run it through a simple test again.
Set the reference time and save your scenario.
Send your Scenario to the Controller:
Send your scenario to the Controller by clicking “Send Scenario”.
(See the IP address/hostname of the Controller that it is connected to at the status bar of ScenarioBuilder.)
Tip: To Manage Controllers/Bases in ScenarioBuilder, click on “View" -> "Options" and then “Base”.
Close or minimize ScenarioBuilder.
LAUNCH APPLOADER CONTROLLER
Either by 1. desktop shortcut or by 2. open a browser to access Controller (by typing in IP address or hostname of the machine controller is on followed by and the port number, For example, localhost:8888 )
Log in to the Controller (default is username: admin, password: admin)
Set up user account details, (it is only required for the first time logging in), submit and log in again.
You will see the Injectors page with your registered Injector.
VERIFY ROBOT USERS (RUSERS)
You should now see 1 connected user.
Tip: If you do not see your user connected (you see 0 instead of 1 under “Connected”), then manually start VStation process by going to the Injector installation folder (...\Automai\Injector) and double-clicking on “VStation.exe”.
CREATE and EXECUTE TESTS
Launch AppLoader Controller.
Click on "Manage Tests" tab
Click "Create new test plan"
Enter a name and description for your test plan.
*For further explanation, hover over the field names.
- Steady-state time: How long (in minutes ) you want your test to run after all the rUsers are on the system)
Use 10 minutes as the default.
- Enforce SST (Steady-state time): “No” allows you to specify the number of iterations you want under "Test Scenario" section. “Yes” stops executing test at the set time.
Test scenario section:
Select desired Injectors, scenarios, rUsers, delay, pacing (using dropdown, or wizard)
The number of iterations is automatically calculated. You can change this if you don’t enforce steady-state time.
If have any CSV files in your script, it will show up in this section. Choose how you want AppLoader to use (For example for usernames, use “Fixed row per User”.)
Hover over “Access Rule” for more explanation or see AppLoader User Guide.
Click “Yes”, to review the execution plan.
Close execution plan window and click YES
Rename the load test if desired, and add notes (i.e. Load test run 1) on the test plan.
Check Send Scenario, and Submit.
MONITOR LOAD TEST EXECUTION
Once the test starts, the real-time page will open.
The test is running n the user desktops.
VIEW and ANALYZE REPORTS
Go to "Test Analysis" Controller to view and analyze load test results, failures, reports, etc.
If there are script failures, go back to ScenarioBuilder and fix them as needed. Resend your scenarios and execute your tests again.
Once the test runs smoothly, you can go to 5 user test on a server.
Contact us anytime for assistance! firstname.lastname@example.org.