AgileLoad Script Editor is where the HTTP conversation between the client and 1st level server is captured, edited & verified. AgileLoad Script Editor is launched from the start menu and can be found in the same folder as AgileLoad Starter. Once a script has been opened you will see that AgileLoad Script Editor has a record button, by default it will use integration with Internet Explorer, there are a number of alternative capture methods which will be covered in the advanced section of Test Scenario Creation.
To make the capture using AgileLoad Script Editor hit the record button. By default this will launch Internet Explorer along with the Script Capture Bar; at this point you need to enter the URI (address) of the application you want to test. Here we’ve used aws.amazon.com/ec2
Navigate through your application as usual and you will see the number of requests go up as HTTP requests are captured. You have options to add timers, comments and screenshots using this bar. More information can be found in the AgileLoad online help about this. Once your recording session is complete hit the stop button. AgileLoad at this point will then pop up with a dialog box that has tried to guess the type of technology that is in use. It does this to enable it to correctly parametrise the script for things such as session id’s, viewstates and other session variables. These models can be edited and new models can be created, this is covered in advanced script editing.
Once AgileLoad Script Editor has parametrised the script you will see the script editor itself. The interface is divided into four quadrants. The upper left is the script, the lower left is the output / multifunction window. The right hand side of the screen is the HTTP data half of the screen which is divided into an upper half, which shows the current main HTTP request we are viewing and any relative sub requests, and a lower half which shows the actual HTTP received data in various formats including rendered HTML (as you would see it in a browser), HTML source, binary, tree view and more. The other function of the lower half of the window is to show the HTTP request data – the HTTP request that the browser made during capture or that AgileLoad made during replay.
If you find that after capture your page is not rendering properly, it may be because there is JavaScript or ActiveX running in the page. There are some ways to control how the content is displayed in Options -> HTML view. Please note that this is only a display of rendered HTML and does not affect the way that the HTTP requests will be replayed in the script so do not be concerned of the page is not displaying as you would expect in a browser.
Replaying the Script in Script Editor
To play back the recorded HTTP script click the green ‘play’ button in the toolbar. At this point AgileLoad will execute the script that is currently loaded. All HTTP requests, SLEEP times, checks and parses (uses to correlate properly the session variables) will be executed. The pages will be shown in the HTTP data window as responses are received from the server. If the speed of the script appears to be slow this is probably because of the SLEEP statements in the script (used to reflect user time such as the time to enter a password or fill out a form for example). It is possible in the Replay Options menu item to remove or reduce the SLEEP time during playback.
Once the execution is complete, AgileLoad prompts offering Replay Details, this view is the comparison of the HTTP request and reply chain that was seen during capture with the HTTP request and reply chain that was seen during replay of the script. These two streams should be identical in the main, i.e if the script logged into the application and bought a product, then the replay should have done the same thing. Things that should be different are timestamps, some cookies, session id’s, other state identifiers and order numbers or serial numbers.
The screenshot above is an example of a replay differences screen. In this case there are several differences all graded as level 2 in the left hand side of the upper part of the window. In fact looking at the top right we can see that AgileLoad has replayed the requests with gzip compression. If this is an issue in your test (for example if web server performance and network is the focus rather than application logic) then the settings in AgileLoad Center (see advanced part of that section) will enable gzip (compression) to be disabled.
The lower part of the window shows the request originally made by the browser in the left hand side and the request actually made by the script in the right hand side. Exclamation marks denote differences in the responses, here they are as to be expected relating to cookies, dates and session data.
The tabs relating to the lower view in the window offer client and server views. By default server view is selected, choosing client view will show the HTTP request differences which is a useful view when troubleshooting.
Next Go to Test setup & Run
OR
Next See the Video "Capturing the script
OR
Next Advanced scripting