Answer / mahesh sv

Step 1: Planning the test. Here, we develop a clearly
defined test plan to ensure the test scenarios we develop
will accomplish load-testing objectives.

Step 2: Creating Vusers. Here, we create Vuser scripts that
contain tasks performed by each Vuser, tasks performed by
Vusers as a whole, and tasks measured as transactions.

Step 3: Creating the scenario. A scenario describes the
events that occur during a testing session. It includes a
list of machines, scripts, and Vusers that run during the
scenario. We create scenarios using LoadRunner Controller.
We can create manual scenarios as well as goal-oriented
scenarios. In manual scenarios, we define the number of
Vusers, the load generator machines, and percentage of
Vusers to be assigned to each script. For web tests, we may
create a goal-oriented scenario where we define the goal
that our test has to achieve. LoadRunner automatically
builds a scenario for us.

Step 4: Running the scenario.We emulate load on the server
by instructing multiple Vusers to perform tasks
simultaneously. Before the testing, we set the scenario
configuration and scheduling. We can run the entire
scenario, Vuser groups, or individual Vusers.

Step 5: Monitoring the scenario.We monitor scenario
execution using the LoadRunner online runtime, transaction,
system resource, Web resource, Web server resource, Web
application server resource, database server resource,
network delay, streaming media resource, firewall server
resource, ERP server resource, and Java performance monitors.

Step 6: Analyzing test results. During scenario execution,
LoadRunner records the performance of the application under
different loads. We use LoadRunner?s graphs and reports to
analyze the application?s performance.

Answer / banishree

Step 1: Planning the test. Here, we develop a clearly
defined test plan to ensure the test scenarios we develop
will accomplish load-testing objectives.

Step 2: Creating Vusers. Here, we create Vuser scripts that
contain tasks performed by each Vuser, tasks performed by
Vusers as a whole, and tasks measured as transactions.

Step 3: Creating the scenario. A scenario describes the
events that occur during a testing session. It includes a
list of machines, scripts, and Vusers that run during the
scenario. We create scenarios using LoadRunner Controller.
We can create manual scenarios as well as goal-oriented
scenarios. In manual scenarios, we define the number of
Vusers, the load generator machines, and percentage of
Vusers to be assigned to each script. For web tests, we may
create a goal-oriented scenario where we define the goal
that our test has to achieve. LoadRunner automatically
builds a scenario for us.

Step 4: Running the scenario. We emulate load on the server
by instructing multiple Vusers to perform tasks
simultaneously. Before the testing, we set the scenario
configuration and scheduling. We can run the entire
scenario, Vuser groups, or individual Vusers.

Step 5: Monitoring the scenario. We monitor scenario
execution using the LoadRunner online runtime, transaction,
system resource, Web resource, Web server resource, Web
application server resource, database server resource,
network delay, streaming media resource, firewall server
resource, ERP server resource, and Java performance monitors.

Step 6: Analyzing test results. During scenario execution,
LoadRunner records the performance of the application under
different loads. We use LoadRunner.s graphs and reports to
analyze the applications performance.

Explain the difference between automatic correlation and manual correlation?

0 Answers  

---

What is the vuser in the scenario?

0 Answers  

---

for suppose if you are selected for individual project, how will you manage the project like, how will you find critical scenario's in your project ?

1 Answers   HCL,

---

Describe configurations of both servers? Here what r two different servers.

3 Answers   EDS,

---

Application Description: My current Project is a .net application & has Active X components also implements AJAX technology for report generation. Flow : A report has to be generated as soon as the preferences have been selected. Issue With Web(http/html) protocol in LR 8.1.4 and LR 9.1: Replay snap shot doesn't show any screens except the login screen(junk data is displayed instead of Reports)..And the last snap shot has "session expired" messsage. Issue with Web(click and Script) Able to record and replay sometimes...but no consistentency. Couldn't execute the script in the controller due to this incosistency. Any suggestions would be really helpfull.E-mail me for any further clarifications/information.

2 Answers  

---

pls suggest me a good institute for loadrunner in hyderabad also what about a practice project?

15 Answers  

---

how to download pdf file in loadrunner

3 Answers   Sears Holdings,

---

can u name some of the important functions in LoadRubber Scripting?

1 Answers   CTS,

---

What r the arguments in lr_set_debug function

3 Answers   Symphony,

---

What is the loadrunner end transaction and its syntax?

0 Answers  

---

When a business transaction, is run in LR and QTP (the response time= same for both 2 sec , No of user = 1). Which tool would you opt for???

3 Answers   Keane India Ltd,

---

What is Performance testing?

5 Answers  

---