If you have used performance testing tools before then please skip the AgileLoad Starter section and move to the Script Editor section.
A script could also be considered as an user journey, customer transaction or scenario capture. In fact it is the result of a session that you have recorded in AgileLoad that contains a list or ‘script’ of user actions such as ‘login’, ‘search’, ‘add to basket’, ‘make trade’ etc.
AgileLoad starter was created to enable a complete novice to capture a simple script, run that script as part of a test and take a look at the results. Once you are experienced with AgileLoad you will naturally progress to using AgileLoad Script Editor and Center. This section describes the process of capturing a script only. The Test Execution section describes how to run a test.
If you haven’t already, launch AgileLoad Starter. You can find this on the start menu (see screenshot above). The Starter will take you through the steps to create a test and execute it; here we will only go as far as to capture the script.
AgileLoad Starter launches and at this point you have the opportunity to enter your scenario name and the URI / URL (address) of the application that is the target of the test. Once you have entered that information hit the record button. In this case we called the test My 1st Test and the target is the Amazon EC2 site.
When you hit the record button AgileLoad Starter will start the recording the user actions. You will see AgileLoad Script Editor and Internet Explorer have launched, also you will see the Script Capture Bar and you should see that a number of requests have been captured (please see screenshot below).
Navigate through the application as you normally would considering that every action you make (each HTTP request you induce the browser to make) is being recorded, so it’s best to make sure you make no mistakes as these will be replicated (tens, hundreds or thousands of times) when you come to running your load test.
When you’ve finished hit the stop button (see screenshot) on the Script Capture Bar.
Now you have captured your script AgileLoad will attempt to add logic to ensure that any technical parameters such as session id’s are handled properly. The Session Identifiers Management dialog box will pop up (see screenshot below). AgileLoad will automatically identify the correct model so here you can just click OK. At this point AgileLoad will parameterize your script. This may take a few seconds or minutes depending on the complexity of your application, the length of your script and the technical capability of the computer that you are running AgileLoad on.
Once the parametrisation done your script is complete and can be played back to validate it. You can do this from AgileLoad Starter by hitting the Play button (please see the screenshot below). Don’t worry if you can’t see AgileLoad Starter – it’s probably just behind another window. You can of course at this point choose to Edit the script. This will take you to the AgileLoad Script Editor.
Please see the AgileLoad Script Editor section for more information on how to edit scripts. That section talks about the essentials of script editing while the advanced section advises on how to deal with more complex scripts.
After hitting Play you will see the script execute inside AgileLoad Script Editor, we’ll go into more detail about this in the AgileLoad Script Editor section. Once the script has executed you’ll see that you are prompted to look at the replay differences. This enables you to compare the:
In the main the conversations should be the same barring of course some cookies, session identifiers, timestamps etc. Again this is explained further in the AgileLoad Script Editor Section.
The key thing to look for is whether the script completed the steps correctly, for example if you logged on, was AgileLoad able to log on i.e. did it get past the login screen. If not then it may be necessary to edit the script.
Next Script Editor