Loadrunner Custom Code to select more check box values

Note: checkboxvalueRaw is the list of correlated values which is being listed in the check boxes. It has to be checked in random numberr and submitted.

int i, j;

char checkboxvalue_param[100],temp_param[60], temp1_param[60];

web_reg_save_param(“checkboxvalueRaw”,”LB=XXXXX”,”RB=YYYYY”,”ORD=ALL”,”Notfound=warning”,LAST);

          i=1;

          j=(rand()%(atoi(lr_eval_string(“{checkboxvalueRaw_count}”)))+1);

          lr_output_message (“i is %d, j is %d”, i,j);

          do     

                   {        sprintf (checkboxvalueRaw_param, “{checkboxvalueRaw_%d}”, i);

                             lr_save_string(lr_eval_string(checkboxvalueRaw_param), “checkboxvalue_sel”);

                             strcpy(temp_param, temp1_param);

                             strcat(temp_param, lr_eval_string(“{checkboxvalue_sel}”));

                             if (i<j)

                             {

                                      strcat(temp_param, “,”);

                             }

                             strcpy(temp1_param, temp_param);

                             i=i+1;

                   }

                   while (i==j);

lr_save_string(lr_eval_string(temp_param), “checkboxvalue_sel”);

Loadrunner code to write a string in a file

char newvalue[15]=”I Love India”;

long pfile;

char *filename = “C:\\Sample.txt”;

pfile = fopen( filename,”a+” );

if(pfile == NULL)

{

printf( “Error in opening the filename – %s “,filename );

}

fputs(newvalue,pfile );

fputs( “\n”,pfile );

fclose( pfile );

Hp-Sitescope Vs Hp-Diagnostics

Hp-Sitescope

(1) Agentless monitoring tool

(2) No memory consuming tool.

Hp-Diagnostics

(1) Agent required tool

(2) Memory will be consuming in the monitoing servers. Even this may tend to affect the performance of the web application.

Loadrunner – Agent Issue

Issue: After the scenario has been set up with certain load generators, while starting the scenario we face some errors due to Load generators.

Solution: Note the scripts for which the particular load generator has been used. Open the .prm file for the particular scripts. We can see the mismatch of parameterization name from the script to the prm file of the corresponding script. Now modify the parameter name which is correctly given during parameterization in the script.

Once it is changed and restart the scenario, it will run successfully.