LoadRunner paramater The data generation rule in the load test is done in the previous period
Performance Testing, a unique number parameter type is used for business-based requirements. The business of scripting is to register to start with Alien, followed by digital user account, fill in the relevant account information, submit enterprise information for review. Where the user account is alien at the beginning of stitching a unique number of parameters, the following to the unique numbers of the relevant interpretation, first quoted official information: (I believe you also understand the meaning of this paragraph) Unique number:assigns a range of numbers to B E used for each vuser. You specify the start value and the block size (the amount of a unique numbers to set aside <br>for each vuser). For example, if specify a start value of 1 and a block size of the first vuser can use the numbers 1 to Econd VUser can use<br>the numbers 201-300, etc first run the scene with 50 virtual users (not set duration, iteration 10 times) To verify the official explanation. When the scene runs out, it will go
DatabaseThe registered data is inserted in the This makes it possible to verify with PL/SQL. The PL/SQL block contents are as follows:
| Declareresult VARCHAR (1024); TYPE Myrecord is RECORD (RES t_user. Fuserid%type); Rec_1 Myrecord; Beginselect DECODE (MOD (MAX (To_number (SUBSTR (Fuserid, 6, LENGTH (Fuserid)), 99999999), 0,max (To_number (SUBSTR ( Fuserid, 6, Length (Fuserid)), 99999999)/100,round (MAX (To_number (SUBSTR, 6, Length (Fuserid)), 99999999)/100 + 0.5,0) to Rec_1.resfrom T_user twhere Fuserid in (SELECT a.fuserid from Yh_qyjcxx A WHERE a.qymc like ' Enterprise alien% '); For I in 1.. Rec_1.res Loopselect Wmsys. Wm_concat (' Alien ' | | SUBSTR (Fuserid, 6, LENGTH (Fuserid))) into Resultfrom t_user bwhere B.fuserid in (SELECT a.fuserid from Yh_qyjcxx A WHERE a.q YMC like ' Enterprise alien% ') and SUBSTR (Fuserid, 6, Length (Fuserid))/<= Iand SUBSTR (Fuserid, 6, Length (Fuserid))/ ; I-1order by To_number (SUBSTR (Fuserid, 6, LENGTH (Fuserid)), 99999999);D bms_output. Put_Line (' Virtual user ' | | I | | ' The resulting data is: ' | | RESULT); END LOOP; END; |
The results of the program run as follows:Because the size of start is set to 1,block size per ... is set to 100, so the starting data for virtual User 1 is alien1, the starting data for virtual User 2 is alien101, and the starting data for virtual User 3 is alien201 ... The starting data for virtual User 10 is alien4901. Because Paramater is set to be updated for each iteration, it iterates 10 times in the scene, resulting in data such as Alien2, alien102.....alien4902. This is consistent with the official explanation. Note: With a skeptical attitude to verify that the relevant rules and principles of loadrunner in-depth analysis, will understand more thoroughly.
LoadRunner paramater data generation rules in load testing
