Interested to Buy Any Domain ? << Click Here >> for more details...
hi
i want how to know how to explain the load runner process
please explain iam having the interivew
- 2 Answers
- 5705 Views
- I also Faced
- E-Mail Answers
Answer Posted / narayan singh
Load testing typically consists of five phases:
1) Planning 2)Script creation 3)Scenario definition 4)
Scenario execution and 5) Results Analysis.
> Plan Load Test - Define your performance testing
requirements, for example, number of concurrent users,
typical business processes, and required response times.
> Create Vuser Scripts - Capture the end-user activities
into automated scripts.
> Define a Scenario - Use the LoadRunner Controller to set
up the load test environment.
> Run a Scenario - Drive, manage, and monitor the load test
from the LoadRunner Controller.
> Analyze the Results - Use LoadRunner Analysis to create
graphs and reports and evaluate the performance.
"Extract from LoadRunner Tutorial - 9.5"
| Is This Answer Correct ? | 5 Yes | 2 No |
Post New Answer View All Answers
What protocols does loadrunner support?
how to get current system time Loadrunner function?
What is difference between manual scenario and goal oriented scenario?
What would be your recommendation to improve performance measure?
How does caching affect performance testing results?
How can we develop the database vuser script?
How will you divide your script into multiple actions? Why?
When loadrunner is used?
How is each step validated in the script?
Can anyone please mention what are the common errors that we can see while replaying the Vugen script and also while running the controller scneraio and How to handle them with a few examples. This will be greatly helpful.
What are the different types goals in goal-oriented scenario?
How you set maximum number of vuser that a host can run?
Which protocols are supported by loadrunner?
What is the latest version and language used in load runner?
You want to have each step in your script measured as a transaction in the controller and not shown in the replay log in vugen. How can you accomplish this?
