Loadrunner flow step by step

Load Runner is a performance testing tool.
It also does functional testing.

Load Runner has 4 components:

Ø Virtual User Generator (VUGEN)
Ø Controller
Ø Analysis
Ø Load Generator.

1) VUGEN:
VUGEN is where we
a) Record, b) Run, c) Debug & d) Design.
They are called Vuser scripts.

2) Controller:
Controller is where we apply the load. The Controller organizes drives, manages and monitors the load test.

3) Analysis:
Analysis is where we analyze the performance results.

4) Load generator/Launcher:
It is the local host [which is CPU]. Load generator generates the load by running virtual users.

Load Runner has 2 views:

1) Script view
2) Tree view: It has 2 vies as well:- a) Page view & b) HTML view

To start:
Ø Go to Programs
Ø Load Runner
Ø Virtual User Generator
Ø Click on “New file”
Ø Expand E Business
Ø Select “Web(HTTP/HTML)”
Ø Click “OK”
Ø Highlight “Action”
Ø Click “Record”
Ø Type URL[www.Macy’s.com]
Ø Click “OK”

Then run from the top. Result summary appears. Status =”Passed”.
On the left window expand the “Iteration” to watch the screens. Then close the result window.
Delete cookies and design.
To design we have write “Comments” and “Start” and “End” transactions.
To write comments:
Ø Go to “Insert”
Ø Click on “Comment” and write the comment
E.g. “Type www.Macy’s.com.” and the main page of Macy’s will open.”
Then click on the icon “Start transaction” and write “Macy’s” and enter. At the end of that script click on the icon “End transaction” and it will automatically have “Macy’s”, just enter. Similarly we have to do it to every link. After we are done we have to run again and save the test case with a name.

Toggle Break point

Using the Toggle Break point we can stop the script where ever we want. But it has some limitations. We can use TBP only before “web_url” & “web_ txt”. Using the Toggle Break point we can do line by line debugging. After debugging we design the script.

There are 3 kinds of errors:

1) Syntax error: [ , ; : “ ) ] etc.
2) Runtime error: Spelling error.
3) Compiling error:

Syntax error and Runtime error are tester’s responsibility.
Compiling error is programmer’s responsibility.
Toggle Break point is only for Runtime error. The TBP looks like a hand symbol. If we put TBP anywhere besides web_url or web_txt the system won’t recognize it and it will run through without stopping. After designing we can put Toggle Break Point before “LR_start_transaction”. If we put TBP before “LR_end_transaction” it will work but it is better to stop it at start. Sometimes we are not sure about some scripts whether to delete it or not. In that case first put it under comment and run. If it works then delete it. By using TBP we can do line by line debugging. Toggle Break Point is only for runtime error.
We can check the Pass/Fail log in the “Replay log”.

Business Analyst Faq .com

Loadrunner flow step by step