Mercury load runner


Published on

LoadRunner Manual

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Mercury load runner

  1. 1. Mercury LoadRunner TestingQA
  2. 2. CONTENTS What is Performance Testing? Introducing Mercury LoadRunner LoadRunner Terminology Mercury LoadRunner Components Steps in LoadRunner Testing Process LoadRunner Virtual User Generator Mercury LoadRunner Controller Mercury LoadRunner Analysis
  3. 3. What is Performance Testing?  Performance testing focuses on the volume, load, scalability and stability of the underlying software architecture and hardware in real-time environments. This includes the various software components software and application servers, hardware servers and network components that make up today's complex software systems. 3
  4. 4. Introducing Mercury LoadRunner  LoadRunner is a tool used to emulate an environment where multiple users work concurrently. While the application is under load, LoadRunner accurately measures and analyzes the system performance, and its functionality
  5. 5. LoadRunner Terminology Scenarios Using LoadRunner, you divide your application performance testing requirements into scenarios. A scenario defines the events that occur during each testing session. For example, a scenario defines and controls the number of users to emulate, the actions that they perform, and the machines on which they run their emulations. Vusers In the scenario, LoadRunner replaces human users with virtual users or Vusers. When you run a scenario, Vusers emulate the actions of human users —submitting input to the server. A scenario can contain tens, hundreds, or even thousands of Vusers.
  6. 6. LoadRunner Terminology Vuser Scripts The actions that a Vuser performs during the scenario are described in a Vuser script. When you run a scenario, each Vuser executes a Vuser script. The Vuser scripts include functions that measure and record the performance of the server during the scenario. Transactions To measure the performance of the server, you define transactions. Transactions measure the time that it takes for the server to respond to tasks submitted by Vusers.
  7. 7. LoadRunner Terminology Rendezvous Points You insert rendezvous points into Vuser scripts to emulate heavy user load on the server. Rendezvous points instruct multiple Vusers to perform tasks at exactly the same time. For example, to emulate peak load on the bank server, you insert a rendezvous point to instruct 100 Vusers to simultaneously deposit cash into their accounts. Controller You use the LoadRunner Controller to manage and maintain your scenarios. Using the Controller, you control all the Vusers in a scenario from a single workstation.
  8. 8. LoadRunner Terminology Hosts When you execute a scenario, the LoadRunner Controller distributes each Vuser in the scenario to a host. The host is the machine that executes the Vuser script, enabling the Vuser to emulate the actions of a human user. Performance Analysis Vuser scripts include functions that measure and record system performance during load-testing sessions. During a scenario run, you can monitor the network and server resources. Following a scenario run, you can view performance analysis data in reports and graphs.
  9. 9. Mercury LoadRunner Components  Virtual User Generator (VuGen)  LoadRunner Controller  LoadRunner Analysis
  10. 10. Steps in LoadRunner Testing Process Plan the test  Plan the test  Create Vuser scripts  Create controller scenario Create Vuser Scripts Create Controller Scenario  Run the scenario  Monitor the scenario Run the Scenario  Analyze the results Monitor the scenario Analyze the results
  11. 11. LoadRunner Virtual User Generator VuGen Code View VuGen Script Editor Logs
  12. 12. LoadRunner Virtual User Generator Section of Script Vuser_init Action Vuser_end Sections
  13. 13. LoadRunner Virtual User Generator Developing Vuser Scripts Walk through the scenario to be scripted Record the scenario Edit or enhance the script Configure the runtime settings Run the Vuser script Re-enhance and re-run till working properly Incorporate the script into LR scenario
  14. 14. LoadRunner Virtual User Generator Scripting Mainly ‘C’ Programming Language Based Able to incorporate ‘C’ looping structures (for, if, while,…) Can also use Java, JavaScript, VB and VBScript Script Enhancements Transactions Parameterization Rendezvous Points Think Time
  15. 15. LoadRunner Virtual User Generator Defining User Behavior Recording Options      Recording Browser Recording Proxy Advanced Correlation Runtime Settings  General  Network  Browser  Internet Protocol
  16. 16. Mercury LoadRunner Controller New Scenario: Manual Scenario Percentages Option Goal Oriented Scenario
  17. 17. Mercury LoadRunner Controller Controller Design Tab Scenario Schedule Section (Manual Scenario) Edit Schedule Scenario Scenario Group Section (Manual Scenario) Run Tab
  18. 18. Mercury LoadRunner Controller Configurations on Design Tab Edit Schedule Setting Up the Rendezvous (If Any) Runtime Settings Load Generators No of Vuser per Script
  19. 19. Mercury LoadRunner Controller Controller Run Tab Scenario Status Scenario Groups Available Graphs Tree Graph Viewing area Online Monitor Graphs Graph Legend
  20. 20. Mercury LoadRunner Controller Monitoring at Scenario Run In Scenario Status you can monitor the errors and number of transactions done. In Scenario Groups you can monitor what any particular group of users are doing. You can monitor the different graphs In the graph viewing area. Legends area will have whatever measurements that you have added and what color on the graph represents each measurement.
  21. 21. Mercury LoadRunner Analysis Analysis Summary Available Graphs Summary Report Data with Legend
  22. 22. Mercury LoadRunner Analysis Viewing a part of scenario You can instruct LoadRunner to calculate graphs and reports based on a part of the scenario. For example, if you have a scenario with a duration of 400 seconds, but you are only interested in the period beginning at 60 and ending with 360 seconds, you can specify that interval in the Time Filter dialog box. After setting the time filter, you must rebuild the result database in order for the changes to take effect.
  23. 23. Mercury LoadRunner Analysis Merging Graph
  24. 24. Mercury LoadRunner Analysis Running Virtual Users Graph The Running Virtual User graph displays the number of Vusers that executed Vuser scripts during each second of a scenario run. This graph is useful for determining the Vuser load on your server at any given moment. The x-axis represents the elapsed time (in seconds) since the start of the scenario run. The y-axis represents the number of running Vusers in the scenario
  25. 25. Mercury LoadRunner Analysis Transactions per Second Graph (Passed) The Transactions per Second (Passed) graph displays the number of completed, successful transactions performed during each second of a scenario run.
  26. 26. Mercury LoadRunner Analysis About Scenario Performance During scenario execution, Vusers generate data as they perform their transactions. LoadRunner allows you to generate graphs that show scenario activity or overall scenario performance. Scenario performance graphs and reports let you analyze Vuser behavior throughout the scenario. The Performance graphs map the transaction response time, and other general information about the scenario.
  27. 27. Mercury LoadRunner Analysis Transaction Response Time (Percentile) The Percentile graph analyzes the percentage of transactions that were performed within a given time range. This graph helps you determine the percentage of transactions that
  28. 28. Mercury LoadRunner Analysis Transaction Response Time Under Load Graph The Transaction Response Time Under Load graph indicates transaction response times relative to the number of Vusers running at any given point during the scenario.
  29. 29. Mercury LoadRunner Analysis Hits Per Second Graph Displays the number of hits made on the Web server by Vusers during each second of the load test. This graph helps you evaluate the amount of load Vusers generate, in
  30. 30. Mercury LoadRunner Analysis Throughput Displays the amount of throughput (in bytes) on the Web server during the load test. Throughput represents the amount of data that the Vusers received from the server at any given second. This graph helps you to evaluate the amount of load Vusers generate, in terms of server
  31. 31. Mercury LoadRunner Analysis Server and Network Graph(s) Depending on the measurements selected and the server selected LoadRunner produces graphs based on them. Sample: Weblogic and Oracle
  32. 32. Mercury LoadRunner Thank You!