NOTE – if you should encounter issues along the way, please reach out to us for assistance at +1 833-288-6624 (+1 833-AUTOMAI) or firstname.lastname@example.org. We are committed to helping you have a positive trial experience.
1. Add log off steps to your script. When executed multiple times in a run the script will log in over and over, therefore it needs to log off the app before it starts the next execution.
2. Add Begin and End Transactions to your script. To do this, add a Begin Transaction action at the point in the script you want to track as a transaction and give it a meaningful name. Add an End Transaction action at the point where the transaction ends. Select the Begin Transaction name in the Properties Transaction Name drop-down. Repeat this process to cover all the transactions that you want to track. For example, you could add a Begin Transaction before the step that launches the application and an End Transaction after the step where the login page appears. That will provide a transaction time on how long it takes to launch the application.
3. Execute your script multiple times. If it passes all iterations, you are ready to proceed. If it fails, edit your script. If the script can’t successfully execute multiple iterations in ScenarioBuilder it won’t be able to successfully execute in AppLoader. Be sure to set the Reference Time. This value is needed for AppLoader.
4. If your script uses a CSV file, make sure it has enough data to support a 5 minute run including the ramp up and ramp down time. The formula to determine if you have enough data is [420 (5 minute run time plus 1 minute ramp up and 1 minute ramp down in seconds) / Reference Time (in seconds)] rounded up * 5 (users running script). For a script that takes 74 seconds to execute, you would need at least 30 rows of data in your CSV file to support 5 users during a 5 minute test. In the case of the login script, it can be different users, or it can be the same user that logs in over and over again.
5. Verify connectivity to AppLoader.
a. Click the View tab.
b. Click Options.
c. Click the Base tab.
You should see a Type of “AL” with the address for your server. If you don’t see an entry, click Add to add it. Select it and then click Test. If the test is not successful, verify the address and port. If needed, update the entries and click Test.
6. When the script is ready for use and you’ve verified connectivity to AppLoader, click Send Scenario. This will make the script available in AppLoader.
7. Double-click the AppLoader shortcut on the desktop to launch the AppLoader Controller in your default browser.
8. Log in to AppLoader (User Name: admin / Password: admin).
9. Once you login, you will see that the Injector(s) have registered with the AppLoader Controller.
NOTE - if the Injector(s) do not appear on the “Manage Injectors” page, go to the machine(s) where you installed the Injector and Start Injector [Start> All Programs> Injector> Start Injector].
10. On the AppLoader machine, open SStationManager.
11. Click File > New Connection File.
12. In the first row, fill out the fields. Any field not listed below can be left at the default setting.
13. To add the additional Injector machines, click Add and then repeat step 11 to fill out the details.
14. Once all Injector machines have been added, click Save. The connections will start.
15. Click Manage Tests.
16. Click Create New Test Plan.
17. Fill out the form as follows:
18. Click Save. A Success window appears.
19. Click No. The Run Load Test window appears.
20. Click Yes. The Specify Load Test Name appears.
21. Click Submit. The Success window appears.
22. Click OK. AppLoader shifts to the “Real Time” page automatically after submitting the test.
The Real Time page provides a graphical view of the test in progress, from the Controller perspective.
See your rUsers' status as they progress through connected, waiting, playing, and completed stages. Click status icons to drill down rUser by rUser for up-to-the-minute performance results, including where they are in their current scenario and screenshots of any errors they have encountered.
While a test is running, you can view the execution process through rUserManager. Maximize rUserManager to see each rUser session executing scenarios in real time.
WARNING - while it is OK to minimize the rUserManager window, do NOT close it. Doing so will shut down the rUser sessions and stop further execution of the test run.
After a load test has completed, you can analyze the final results from the Test Analysis page. An important part of the load testing process is viewing and studying the results of a test. Get response time graphs and reports, and export complete test data and graphs into an Excel format. See the timing of your transactions, scenarios, and how your rUsers performed.
By now you should have executed a test in your environment against your application. Hopefully you have the confidence to go forth and run more tests with many more users! However, before you start there are a few things you need to consider.
First – if this is a trial version, it only allows for a 5 user test. To continue using the software and ramp up the user count, you’ll need a license for the software and more users. Contact sales at +1 833-288-6624 (+1 833-AUTOMAI) or email@example.com to discuss your needs.
NOTE – if your trial period expired before you had a chance to create and execute a run, contact us at firstname.lastname@example.org for an extension.
Second – Before ramping up the users, you need to make sure your server can handle the load. Your Injector might only handle 50 users. The number of concurrent rUsers that an Injector can handle will depend largely on the resources that are available (CPU and memory), and what each client of the application under test requires.
If you don’t have hardware in house to support a large number of users, don’t worry. Automai offers turn key cloud solutions to handle your load and performance testing needs.
Lastly – there are many more capabilities in AppLoader, so be sure to check out these resources for more information:
Need a Proof of Concept? Our experts will help establish AppLoader’s viability so that your organization, from stakeholders down to data entry clerks, are 100% behind your decision to go forward with AppLoader!
If at any point during your trial you need more help, our technicians are waiting to help you! Don’t hesitate to call our experts at +1 833-288-6624 (+1 833-AUTOMAI) or email Automai Support email@example.com.
For one-on-one help, create a support request at Automai Help Center. A support engineer will follow up with you quickly. If you don't have an account, you can create one - just follow the prompts. When submitting your support request, please provide as much detail as possible. This will help us resolve your issue faster.
We would love to hear your thoughts on AppLoader and your ideas for future features and improvements. Also, occasionally bugs do happen. If you find one, we'll do our best to fix it.
AppLoader navigation pane includes a ticket form for you to submit your problems, questions and suggestions about the product. Let us know what you think!