software testing genius

HP LoadRunner Questions Bank-Q 41 to 50

Welcome to “Software Testing Genius”. Subscribe to my RSS feed for latest content on Software Testing.

HP LoadRunner Questions Bank: Q. 41 to 50

Learn "Controller" Module of HP – LoadRunner through FAQ’s:

Q. 41: What is the effect of Rendezvous points on the running of scenarios as per schedule?

Rendezvous points, if present in a script, interfere with the scheduled scenario run. The scenario will not run as scheduled due to the presence of rendezvous points in the script.

<<<<<< =================== >>>>>>

Q. 42: What are the methods by which we can schedule the enabled Vuser groups in a scenario?

After creating a scenario, we can schedule the enabled Vuser groups to run according to either of the following:

1) As a part of a whole scenario:

When we run a scenario, LoadRunner runs all the Vuser groups enabled in the scenario. The schedule defined for running the scenario is applied to all the Vuser groups concurrently, and LoadRunner applies each action proportionately to all the Vusers groups.

2) As per its own schedule: For each enabled Vuser group in a scenario, we can design a separate execution schedule. We can specify when to start running the Vuser group, how many Vusers to start and stop running within given time intervals, and how long the Vuser group should continue running.

<<<<<< =================== >>>>>>

Q. 43: How many modes are available to us for scheduling the running of scenario?

We can schedule a scenario to run in one of the following modes:

1) Real-life schedule: The scenario runs according to a user-defined group of actions that simulate a real-life schedule of events. Vuser groups run according to the iterations defined in their run-time settings, but we can define how many Vusers to run at a time, how long Vusers should continue to run, and how many Vusers to stop running at a time.

2) Classic Schedule: All enabled Vuser groups run together on one schedule, each according to its own run-time settings. We can schedule how many Vusers to start running at a time, how long to run the Vusers, and how many Vusers to stop running at a time.

3) Run until complete: All the Vuser groups in the scenario run according to the iterations defined in their run-time settings. Each Vuser group in the scenario runs its defined course, and when all the Vuser groups have finished running, the scenario run is complete.

<<<<<< =================== >>>>>>

Q. 44: What is the purpose of specifying Service Level Agreements in scenarios?

While creating a load testing scenario, we can specify our goals or service level agreements - SLA's for the performance measurement.

When this scenario is made to run the LoadRunner captures all the performance related data. During analysis phase, Analysis compares this data against the SLAs and determines SLA status for the defined measurements.

<<<<<< =================== >>>>>>

Q. 45: What methods LoadRunner uses to find out the SLA status?

Depending on the measurements being evaluated by us, LoadRunner finds out the SLA status in one of the following ways:

1) As per time interval within the run: Analysis displays SLA statuses at set time intervals in the timeline. For example, every 10 seconds - Analysis checks to see if the measurement’s performance has deviated from the threshold defined in the SLA.

2) As per the whole run: Analysis displays a single SLA status for the whole scenario run. The measurements include - Total Hits, Average Hits, Total Throughput, and Average Throughput.

<<<<<< =================== >>>>>>

Q. 46: How many types of Goal Oriented Scenarios can be created in LoadRunner?

In a goal-oriented scenario, we define the goals required to be achieved through our tests, and LoadRunner automatically builds a scenario for us based on these goals.

When we want to test how many Vusers the application can run simultaneously, it is better to define a type of goal for the Virtual Users.

Following five types of goals can be defined in a goal-oriented scenario:

1) Defined number of virtual users

2) Defined number of hits per second by the Web Vusers.

3) Defined number of transactions per second.

4) Defined number of pages per minute by the Web Vusers.

5) Defined transaction response time we want our scenario to reach.

<<<<<< =================== >>>>>>

Q. 47: Under what circumstances a Pages per Minute or Hits per Second goal-oriented scenario fails?

Pages per Minute or Hits per Second goal-oriented scenario is assigned a "Failed" status in situations like:

1) When the Controller has twice attempted to reach the goal using the maximum number of Vusers specified, and the goal could not be reached.

2) When no pages per minute or hits or transactions per second were registered after the first batch of Vusers was run.

3) When the number of pages per minute or hits or transactions per second did not increase after the Controller ran a certain number of Vuser batches.

4) When all the Vusers that were run failed.

5) When there were no available load generators for the type of Vusers we attempted to run.

<<<<<< =================== >>>>>>

Q. 48: What is Load Balancing process in LoadRunner?

Load balancing is the process, which evenly distributes the load generated by Vusers among the requested load generators, thereby ensuring an accurate load test.

When a Windows load generator’s CPU usage becomes overloaded, the Controller stops loading Vusers on the overloaded load generator, and automatically distributes them among load generators taking part in the scenario.

Load balancing option is available only in goal-oriented scenarios and manually controlled scenarios in the Percentage Mode.

<<<<<< =================== >>>>>>

Q. 49: What policy attributes can be defined for rendezvous points?

Setting the rendezvous policy determines how the Vusers handle a rendezvous point. We can set the following policy attributes for every rendezvous point:

1) Release policy: Defines how many Vusers will be released from a rendezvous point at a time.

2) Timeout policy: Defines how long the Controller shall wait before releasing Vusers from a rendezvous point.

<<<<<< =================== >>>>>>

Q. 50: Can we disable a particular Vusers at Rendezvous Points?

We can disable a rendezvous point for all Vusers in a scenario.

In addition to this we can disable a rendezvous point for a particular Vusers.

By disabling Vusers at a rendezvous point, we temporarily exclude them from participating in the rendezvous. Enabling disabled Vusers returns them back to the rendezvous.

Continue to Next Part : Q 51 to 60 

Study Material - HP LoadRunner Certification Exams for All Modules

Study Material - HP QTP & QC Certification Exam

Study Material - IBM RFT Certification Exam

What Successful Testers say about the Quality of this website

If you want to keep track of further articles on Software Testing,
I suggest you to subscribe my
RSS feed

You can also Subscribe by E-mail
and get All New articles delivered directly to your Inbox.

Get your Absolutely Free Copy of Several MS PowerPoint Presentations & E-Books related to ISTQB, HP Load Runner, IBM RFT, HP QTP & QC Certification Exams, prepared by Popular Writers & Trainers, by writing to:

Full Study Material for Popular Certification Exams:

Largest Database of Sample Papers - 1000+ Unique Questions for ISTQB Foundation Exam

ISTQB Foundation Exam - Full Crash Course for Download

ISTQB Advanced CTAL Test Analysts Exam - Full Crash Course for Download

ISTQB Advanced CTAL Test Manager Exam - Full Crash Course for Download

Study Material - ISTQB Certification Exam

Consolidated Study Material - Testing & QA

Most Popular Topics in Demand:

Practical Roadmap to QTP Certification

Practical Roadmap to CSTE Certification

General HR Interview Questions Common For All 

Tricky HR Interview Questions Common For All

Rehearsal of QTP in 1 Hr. -  Interview Questions


Comments :


Leave Your Comments: (*) Marked Fields are Mandatory

You can apply basic formatting to the text

Name *
Email Address *
Speak your mind
sex hikayeleri