Adding Scripts and Scenarios

Now that the job is created it must be built up using scripts, configuration and monitors. Monitors will not be covered in this section, for monitoring information please see the advanced section.

To add a script the desired script must be selected then dragged and dropped into the script section of the Job (the middle of the right hand window). In fact when the job was created a window did pop up asking which scripts should be added, of course scripts can be added at that point too.

Once the script is dropped in it will appear as the 1st line of the script section and be set as Script 1 (see right hand column of 1st line). Multiple scripts can be added to one line in order to run them sequentially, also scripts can be added to other lines in the script section where they will run concurrently, in parallel, with the other scripts that make up the job.

The tabs at the bottom of the window relate to task group that is currently selected, so the current view in the screenshot is showing the scheduling for the line that has just been created (in the case the only line).

The next text describes tab by tab the options that are available to configure the behaviour of the scenario, before going into that it’s important to understand how the job scenarios table works. In order to make that clear the next screenshot shows a job with two task groups and three scripts.

 

Looking at the 2nd Task Group highlighted with the blue box, ‘My1stJob_2’ there are two scripts assigned to this group. The group will execute a specified number of transactions (or run indefinitely until told to stop if set to manual stop mode) that the whole group will perform, each script will perform a number of transactions per task group transaction. For example to simulate users that browse 5 items on a site and then buy one product: If the task group is set to 100 transactions and the ‘Browse’ script is set to 5 transactions and the ‘Buy Product’ script is set to 1 transaction in that order, in total we have 100 task group transactions which means 500 ‘Browse’ transactions and 100 ‘Buy Product’ transactions. To understand how many transactions the server will experience multiply those numbers by the number of virtual users set to run that transaction.

 

Next Task group tab
Getting started > Agileload test Center > Adding Scripts and Scenarios
Print this page  -  Go to top of page