Recorder
Parameterization...

To generate dynamic and unique values for each virtual users while simulation process, script has to be parameterized. The figure A shows sample parameters. When particular file is selected, all its existing parameters are displayed in parameter tab.

Figure A

Add: To add new parameter, click Add button, and enter name and value.
Remove: To remove a parameter, select a parameter and click Remove button.
Edit: To edit a parameter, select a parameter and click Edit button and edit name and value.
Parameterization: To parameterize, select a parameter and click Parameterization button. Parameterization window will be opened. (Figure B)

Note: In the above figure the third column Parameterization Function, shows the type of parameterization is used.
For Example: @Default - means this parameter is not yet parameterized, so during simulation default value (recorded value) will be used.
Figure B
In the above figure, the right most pane 'All Modified Parameters' shows the parameters which are already parameterized. It shows FId - File Id, PId - Parameter Id, and parameter name. To update these parameters, select the parameter in the pane, edit and click SET button.

Note: To update parameterization SET button has to be clicked

FUNCTIONS

 @Default - When a parameter is first selected for parameterization by default this function is used, which means its not parameterized so default value (Recorded value) will be used in simulation process. It should be noted here that, to remove the parameterization for a parameter again this function has to be used.

 @FromFile - When this function is selected, browse button option will be enabled, user just has to set the file path. So during simulation process data for each virtual user for this parameter will be fetched from this file. This file should be in line separated format i.e, one value in single line.

For Example: To simulate 10 virtual users, 10 username can be stored in this file, each name in single line. If user provide just 5 names for 10 virtual user then 6th vuser will fetch the first value, 7th will second value and so on.

 @VUserId - This function return its vuser id, only Width field will be enabled for this function.

For Example: If this function is used, vuser 1 will have the value 1, vuser 2 will have the value 2 and so on. We can also specify width field, if width is 3, value will be returned as 001, 002, 003, .. 010.. so on.

 @IterationId - This is similar to above function but it return current iteration count of particular virtual user. Width is allowed for this function.

 @String_VUserId_IterationId - For this function user can enter a String(optional), use underscore(optional) and width(optional).

For Example: sample output from this function
String Width Use "_"  Output
abc 0 checked abc_1_1, abc_2_1, ...
xyz 0 unchecked xyz11, xyz21, ...
pqrs 3 checked pqrs_001_001, ...
  4 unchecked 00010001, 00020001, ...

 @String_IncrementValue_String - Input from user is String1 (optional), Initial Value (optional) if not mentioned 0 is taken as default value, String2 (optional), Use "_" (optional), Width (optional).

For Example: sample output from this function
String Init Val String Width Use "_"  Output
ab 5 xy 0 checked ab_5_xy, ab_6_xy, ...
aaa bbb 0 unchecked aaa0bbb, aaa1bbb, ...
xyz 10 3 checked xyz_010_, xyz_011_, ...
500 xxx 0 unchecked 500xxx, 501xxx, ...

 @String_RndValue_String - Input from user is String1 (optional), Rnd Initial Value (optional) if not mentioned 0 is taken as default value, String2 (optional), Use "_" (optional), Width (optional).

For Example: sample output from this function
String Rnd Init Val String Width Use "_"  Output
abc 100 xyz 0 checked abc_85_xyz, abc_24_xyz, ...
aaa bbb 0 unchecked aaabbb, aaabbb, ...
xyz 50 3 checked xyz_027_, xyz_049_, ...
500 xxx 0 unchecked 399xxx, 249xxx, ...

 @Cookie - In some applications cookie values are used as input for example session id which cannot be generated automatically. Instead the simulator will take the cookie value automatically from the current process. The cookie value will be taken from one of the previous response header.

Here only String field is used to specify the cookie name whose value has to be taken during simulation process.

For Example:

If cookie name is PHPSESSID, the current session id will be automatically taken.
 @UseVariable - Input from the user is only Variable name, from the variable values will be fetched. Befor using a variable, it has to be created. For Example:

In .Net __VIEWSTATE values are posted from the previous page request, so using variable we can fetch the run time values of __VIEWSTATE and post back to the next request.

To Understand Variables Click Here
 @Static - Input from user is one string value which is used by all virtual users.


See Also
Variables
Steps For Parameterization

Trace Technologies Pvt. Ltd.,  Copyright © 2003 - 2008