The parameters in the options tab will determine the behavior of the users in the Task Group scenario including the speed at which they run, the browsers they are using, the requests they might exclude (such as those to sites or applications outside of the test scope) and some technical parameters. Again, it relates to the Task Group scenario that is in focus at the time.
Think time (ms): Think time is the time during which the VU is not active, it is a very important part of the script at it represents user think time such as the time taken to remember a password, to type in the values of a web form or to make a decision. It is vital to make the test realistic and if it is removed the result would be that the generated load simply overloads the server or does not yield any realistic and useable results.
Wait Mode: The wait mode specifies how AgileLoad will deal with SLEEP commands in the script which are automatically inserted as part of the script recording process, or in the case of advanced scripting are inserted or edited by the test specialist. Capture tells AgileLoad to use the same values that are specified in the script. If your scripts were recorded with realistic timing this might be the best option to use, this is also the case if they have been changed in the script to reflect a detailed test plan.
Fixed Value is a way to set the interval between each page request to have a uniform value, for example the users should wait 30s between each action. Other options are variations on random values (controlled by min & max) including Poisson distribution values controlled by lambda, please see the help for more information.
URL Filter: is used exclude requests that are not desired in the playback of the scripts in the Task Group scenario, these may include requests to Doubleclick, Microsoft or Google analytics which would be out of the scope of most tests and could be seen by the targets as a denial of service attack or possible some kind of malicious traffic. A better way to exclude these requests however is the exclude them in the capture phase using the script record options in Script Editor
HTTP Options specify how the users in this Task Group scenario make their requests, including the browser type they should use to form the requests.
Browser Profile can be used to choose a pre-defined browser type or the technical parameters can be manually set.
Type: Use this option to specify the browser that the users for this Task Group scenario are to use. Choose a browser from the list.
Options: If a custom browser is chosen then these technical parameters become available. For information where ‘Capture’ is an option this means the users will use the values coming from the script.
Connections Number: is used to specify how many socket connections should be used by each user to download the page content, this can have a performance impact on the target and it is recommended that the value relating to a specific value is used or the default value is used.
Security: The type of security that is allowed for HTTPS requests.
Version: relates to the HTTP version that should be used to form the request.
Cache: How the users handle cacheable content, useful for simulating load where the target will experience only new users (for example the launch of a an application to the public or part of a television ad campaign), or for simulating a situation with constantly returning users such as an internal intranet application or an application with a loyal user base.
Compress: Whether or not GZip compression will be used.
User-agent: This is the part of the header which describes to the server what type of browser it is and what standards it is following.
Http/s: This is best to be left as default and any HTTPS requests in the scripts will be replayed as such. If a script was recorded in HTTP and security has been out in place this option may be necessary. If HTTPS is selected the Host and Port become available and the target for HTTPS requests should be specified here.
Ignore Static Requests with Extension: Will make sure that users do not make requests with these extensions, useful for running a load test that is light on bandwidth and the web server and where the application logic is the real target. For example if there is a charge for outgoing bandwidth (as with Amazon EC2) this option could be useful if it is known that the web server it not going to be a bottleneck in the test.
No Parse CSS (manage subrequest mode): By default scripts will be using ‘manage subrequest mode’ unless this has been explicitly turned off during the capture process. By parsing the CSS AgileLoad is able to make the requests that would make up the page on the screen without having the requests explicitly in the script, it can however lead to additional requests that were not in the original capture so by default this is left switched off.
Next Network Tab