Krish Hegde 1 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.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
• During a scenario run you can instruct multipleVusers to perform tasks simultaneously by usingrendezvous points. A rendezvous point createsintense user load on the server and enables
LoadRunner to measure server performanceunder load.• You ensure that multiple Vusers act
simultaneously by creating a rendezvous point .When a Vuser arrives at a rendezvous point, it isheld there by the Controller. The Controller releases the Vusers from the rendezvous either when the required number of Vusers arrive, or when a specified amount of time has passed.
• Using the Controller, you can influence the level of server load by selecting: – which of the rendezvous points will be active during the scenario
– how many Vusers will take part in each rendezvous
• For example, to test a bank server you could create ascenario that contains two rendezvous points. The firstrendezvous ensures that one thousand Vuserssimultaneously deposit cash. The second rendezvousensures that another thousand Vusers simultaneously
withdraw cash. If you want to measure how the server performs when only five hundred Vusers deposit cash,you can deactivate (disable) the “withdraw” rendezvous,and instruct only five hundred Vusers to participate in the“deposit” rendezvous.
• Before you run a scenario, you can indicatewhich hosts will run Vusers in the scenario. For example, if a host is unavailable for a particular scenario run, you can exclude it temporarily
instead of removing it entirely from your list of hosts.• You select which hosts will take part in the
scenario by using the Enable and Disablecommands. Disabling a host temporarilyremoves it from the list. Enabling a hostreinstates it.
• Before you run a scenario, you need to specifythe location of the results (mandatory), assign aname to the results, schedule the scenario, andprovide scenario summary information. Inaddition, you can specify the applications toinvoke at the start of a scenario.
• Although most of the pre-scenario settings areoptional, by using them you can enhance thetesting process. These values are scenariospecific—you can set different values for eachLoadRunner scenario.
• When you run a scenario, by default all Vuser information is stored locally on each Vuser host.After scenario execution the results areautomatically collated or consolidated
• To disable automatic collation, choose Results> Auto Collate Results to clear the check markadjacent to the option.
• To manually collate results, choose Results >
Collate Results. If your results have not beencollated, then LoadRunner Analysis willautomatically collate the results beforegenerating the analysis data.
• Open the Scheduler and select an event mode Choose Scenario >Scheduling from the LoadRunner Controller to open the Scheduler andselect the Basic or Expert event modes. The Expert mode allows you to setup dependencies and schedule external events.
• Schedule groups Add existing Vuser groups to the scenario schedule and
set a starting time.• Set the timing properties Set the timing related specifications for thescenario such as duration, initialization, ramp up, and ramp down.
• Create and schedule external events Define delays and external events,and schedule them at the desired points. This setting only applies to Expertevent mode.
• Specify dependencies and sequences. Specify dependencies of one
group upon another or indicate an event sequence. This setting only appliesto Expert event mode.
• Save the schedule and run the scenario. Save the setup and run thescenario from the Scheduler interface. The test runs according to your settings.
TestDirector • LoadRunner works together with TestDirector,
Mercury Interactive’s test management tool.TestDirector provides an efficient method for storing and retrieving scenarios and collecting
results. You store scenarios and results in aTestDirector repository and organize them intounique groups.
• The Controller’s Tools menu contains two menuitems related to TestDirector. The first item,TestDirector Connection changes the testrepository from the standard file system to theTestDirector database. The second item,TestDirector, invokes TestDirector.