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.

What are the process for developing a vuser script?

0 Answers  

---

What are the different sections of the script?

0 Answers  

---

what are the objectivies of performance testing and what is tuning?

1 Answers  

---

we have Unix monitors in LR by default. if i want Linux and Solaris monitors....what i do.. unix is working for Linux and solaris?

1 Answers   HP,

---

What is loadrunner agent?

0 Answers  

---

Does any one know how to over come the problem of "monitoring the load generators over firewall". We are able to use these machines for load generation, but are not able to monitor the measurements of these machines. When tried to add these machines to the windows resources, we were getting the error "Monitor name :Windows Resources. Cannot connect to machine stresstestxp6:62043. Reason: The network path was not found." Also note that, we are able to ping/telnet the LG from the controller, but not the vice versa Is there any router settings to be made or any other configuration has to be done?

1 Answers  

---

Which protocols are supported by loadrunner?

0 Answers  

---

1.What will you do if the VuGen crashes while recording a script? 2.what will you do if Controller crashes while executing a scenario?

2 Answers   IBM,

---

how can u see agent process in controller?

5 Answers   AZTEC,

---

How load runner interacts with the application?

0 Answers  

---

What is parameterization?

0 Answers  

---

what is the difference between Single user and multiple user protocol?

2 Answers  

---