LoadRunner Controller

LoadRunner Controller controls a Scenario and all its components such as Vusers, Hosts, Scripts. LoadRunner Controller plays the role of a Moderator. ie Add & Monitor Vusers. View complete details on Vusers, hosts, Scripts, status etc.

LoadRunner Controller

Create a Scenario

Confi ure Scenario

Step 1:Create a New Scenario & Save the Scenario in a Data Drive. Step 2! Add Vusers Step 3! Add Hosts Step 4! Add hosts to Host List Add Scripts to Scripts List Add Vusers to Vuser "roups Step 5: Configure Scenario

Re#iew Scenario
Re#iew Scenario and all its Components. Chec$ whether the Scenario can fulfill test o%&ecti#es. Re#iew Scenario Confi uration

Add Hosts

Add Scripts

Relati#e paths for Vuser Scripts

'hen you specify the location of a Vuser script, you can specify a relati#e location. (he location can %e relati#e to the current scenario directory, or the LoadRunner installation directory. )ou can specify a path relati#e to the current scenario directory %y typin either of the followin notations at the start of the script path! .* indicates that the path is relati#e to the location of the scenario directory. ..* indicates that the path is relati#e to the location of the parent directory of the scenario directory.

Create Vuser "roups

Create Vusers Rende+#ous ,oints

-urin a scenario run you can instruct multiple Vusers to perform tas$s simultaneously %y usin rende+#ous points. A

rende+#ous point creates intense user load on the ser#er and ena%les LoadRunner to measure ser#er performance under load. )ou ensure that multiple Vusers act simultaneously %y creatin a rendezvous point. 'hen a Vuser arri#es at a rende+#ous point, it is held there %y the Controller. (he Controller releases the Vusers from the rende+#ous either when the re.uired num%er of Vusers arri#e, or when a specified amount of time has passed.

Rende+#ous ,oints
/sin the Controller, you can influence the le#el of ser#er load %y selectin !
0 0 which of the rende+#ous points will %e acti#e durin the scenario how many Vusers will ta$e part in each rende+#ous

1or e2ample, to test a %an$ ser#er you could create a scenario that contains two rende+#ous points. (he first rende+#ous ensures that one thousand Vusers simultaneously deposit cash. (he second rende+#ous ensures that another thousand Vusers simultaneously withdraw cash. 3f you want to measure how the ser#er performs when only fi#e hundred Vusers deposit cash, you can deacti#ate 4disa%le5 the 6withdraw7 rende+#ous, and instruct only fi#e hundred Vusers to participate in the 6deposit7 rende+#ous.

Confi ure Scenario

8efore you run a scenario, you can confi ure %oth the host and Vuser %eha#iors for the scenario. (he default settin s correspond to most en#ironments.

Runtime Settin s Confi ure 9utput file Set timeout

LoadRunner ena%les you to set the timeout inter#al for commands, pin in of hosts, and Vuser elapsed time. (he command timeouts relate to hosts and Vusers. (he host commands for which you can specify a timeout inter#al are Connect, -isconnect, and Heart%eat. (he Vuser commands for which you can specify a timeout inter#al are 3nit, Run, ,ause, A%ort.

Set 1ile path

 'hen you run a scenario, %y default the run:time files are stored locally on each Vuser host. 4the machine runnin the Vuser script5 (he default location of the files is under the temporary directory specified %y the host;s en#ironment #aria%les.

Confi ure Hosts

8efore you run a scenario, you can indicate which hosts will run Vusers in the scenario. 1or e2ample, if a host is una#aila%le for a particular scenario run, you can e2clude it temporarily instead of remo#in it entirely from your list of hosts. )ou select which hosts will ta$e part in the scenario %y usin the <na%le and -isa%le commands. -isa%lin a host temporarily remo#es it from the list. <na%lin a host reinstates it. Host ta%=-etails=Vuser limits

Set Ma2 Vuser for Host ,reparin to run Scenario

8efore you run a scenario, you need to specify the location of the results 4mandatory5, assi n a name to the results, schedule the scenario, and pro#ide scenario summary information. 3n addition, you can specify the applications to in#o$e at the start of a scenario. Althou h most of the pre:scenario settin s are optional, %y usin them you can enhance the testin process. (hese #alues are scenario specific>you can set different #alues for each LoadRunner scenario.

Specify results location

'hen you run a scenario, %y default the runtime files are stored locally on each Vuser host. After the scenario, the results are collated to ether and processed on the Controller machine. Alternati#ely, you can instruct LoadRunner to sa#e the results on a shared networ$ dri#e.

Specify results location /sin (est -irector

1 Choose Options = TestDirector Connection to open a connection to a (est-irector ser#er and data%ase.

2 9pen an scenario from the data%ase 4 i!e = Open5, or sa#e the current scenario to the (est-irector data%ase 4 i!e = Save "s5.

Collatin Results
'hen you run a scenario, %y default all Vuser information is stored locally on each Vuser host. After scenario e2ecution the results are automatically collated or consolidated (o disa%le automatic collation, choose #esu!ts = "uto Co!!ate #esu!ts to clear the chec$ mar$ ad&acent to the option. (o manually collate results, choose #esu!ts = Co!!ate #esu!ts. 3f your results ha#e not %een collated, then LoadRunner Analysis will automatically collate the results %efore eneratin the analysis data.

Schedule Scenario Run

After you create a scenario, you select the "roups and Vusers that you want to participate in the scenario and run it manually from the Controller. Alternati#ely, you can use the LoadRunner Scheduler to set up a scenario to run automatically. )ou can set the start and duration time of the scenario and indicate which "roups should participate in the scenario. (his chapter descri%es!

Schedule Scenario Run

Open the Sche$u!er an$ se!ect an event %o$e Choose Scenario & Sche$u!ing from the LoadRunner Controller to open the Scheduler and select the 8asic or <2pert e#ent modes. (he <2pert mode allows you to set up dependencies and schedule e2ternal e#ents. Sche$u!e groups Add e2istin Vuser roups to the scenario schedule and set a startin time. Set the ti%ing properties Set the timin related specifications for the scenario such as duration, initiali+ation, ramp up, and ramp down. Create an$ sche$u!e e'terna! events -efine delays and e2ternal e#ents, and schedule them at the desired points. (his settin only applies to <2pert e#ent mode. Specif( $epen$encies an$ se)uences. Specify dependencies of one roup upon another or indicate an e#ent se.uence. (his settin only applies to <2pert e#ent mode. Save the sche$u!e an$ run the scenario. Sa#e the setup and run the scenario from the Scheduler interface. (he test runs accordin to your settin s.

Mana in Scenario usin (est-irector

LoadRunner wor$s to ether with (est-irector, Mercury 3nteracti#e;s test mana ement tool. (est-irector pro#ides an efficient method for storin and retrie#in scenarios and collectin results.

)ou store scenarios and results in a (est-irector repository and or ani+e them into uni.ue roups. (he Controller;s Too!s menu contains two menu items related to (est-irector. (he first item, TestDirector Connection chan es the test repository from the standard file system to the (est-irector data%ase. (he second item, TestDirector, in#o$es (est-irector.

9pen connection to (est-irector 9pen Scenario from (est-irector

Sa#e Results in (est-irector

8efore you run a scenario, you set the results location. 3f you ha#e a connection open to the (est-irector pro&ect, results are sa#ed to the default test set. )ou can also sa#e the results to a new or e2istin test set, or to dis$ usin the standard file system.

?uestions@