Jump to content

LoadRunner: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Line 41: Line 41:
HP LoadRunner uses Correlation to handle dynamic content. Dynamic content refers to page components that are dynamically created during the execution of a business process, and the value may differ from the value generated in a previous run. Examples of dynamic content include the ticket number in an on-line reservation system, a transaction ID in an on-line banking application and most importantly the unique session ID that is created each time a user logs in. Such dynamic values must be correlated in order to run the recorded script. The script while running will return an error if such a dynamic value has not been correlated, since the value changes each time the user logs in.
HP LoadRunner uses Correlation to handle dynamic content. Dynamic content refers to page components that are dynamically created during the execution of a business process, and the value may differ from the value generated in a previous run. Examples of dynamic content include the ticket number in an on-line reservation system, a transaction ID in an on-line banking application and most importantly the unique session ID that is created each time a user logs in. Such dynamic values must be correlated in order to run the recorded script. The script while running will return an error if such a dynamic value has not been correlated, since the value changes each time the user logs in.


If the dynamic content is a part of a previous server response, LoadRunner can correlate that value with future instances in which it must be sent back to the server. HP LoadRunner saves the changing values into parameters, which are used during emulation.<ref>[http://www.slideshare.net/guru__123/loadrunner-presentation “LoadRunner Presentation.” Retrieved 2010-03-05.]{{dead link|date=December 2010}}</ref>
If the dynamic content is a part of a previous server response, LoadRunner can correlate that value with future instances in which it must be sent back to the server. HP LoadRunner saves the changing values into parameters, which are used during simulation.<ref>[http://www.slideshare.net/guru__123/loadrunner-presentation “LoadRunner Presentation.” Retrieved 2010-03-05.]{{dead link|date=December 2010}}</ref>


==Controller==
==Controller==

Revision as of 10:47, 8 March 2012

For the video game, see Lode Runner. For the Citroën CX Loadrunner, see Citroën CX.
HP LoadRunner
Developer(s)Hewlett-Packard, HP Software Division
Stable release
11.0
Operating systemMicrosoft Windows and Unix (Load Generator only)
TypeLoad testing tools
LicenseProprietary
WebsiteHP LoadRunner software

HP LoadRunner is an automated performance and testing product from Hewlett-Packard for examining system behaviour and performance, while generating actual load.[1] HP acquired LoadRunner as part of its acquisition of Mercury Interactive in November 2006.[2] HP LoadRunner can emulate hundreds or thousands of concurrent users to put the application through the rigors of real-life user loads, while collecting information from key infrastructure components (Web servers, database servers etc.)[3] The results can then be analyzed in detail, to explore the reasons for particular behavior. HP LoadRunner is sold as part of the HP IT Management Software category by the HP Software Division.

Consider the client-side application for an automated teller machine (ATM). Although each client is connected to a server, hundreds of ATMs may be open to the public. During peak times — such as 10 a.m. Monday, the start of the work week — the load may be much higher than normal. In order to test such situations, it is not practical to have a testbed of hundreds of ATMs. So, one can use an ATM simulator and a computer system with HP LoadRunner to simulate a large number of users accessing the server simultaneously. Once activities are defined, they are repeatable. After debugging a problem in the application, managers can check whether the problem persists by reproducing the same situation, with the same type of user interaction.

HP LoadRunner consists of several different tools: Virtual User Generator (VuGen), Controller, Load Generator, Analysis and the AJAX TruClient (new with V.11.0).[4]

Virtual User Generator

The Virtual User Generator (VuGen) ) is used to simulate the steps of real human users. VuGen can also run scripts for debugging.[5] VuGen lets the user record and/or script a test to be performed against an application under test, and play back and make modifications to the script as needed, such as defining Parameterization (selecting data for keyword-driven testing).[6]

HP LoadRunner supports more than 51 protocols including Web HTTP/HTTPS, Remote Terminal Emulator, Oracle and Web Services.[7] A protocol acts as a communication medium between a client and a server. For example an AS400 or mainframe-based application can use a terminal emulator to talk to a server, and an on-line banking application can use HTTP/HTTPS with some Java and Web services. LoadRunner can record scripts in both single and multi-protocol modes.[8]

During recording, VuGen records a tester's actions by routing data through a proxy.[9] The type of proxy depends upon the protocol being used and affects the resulting script. For some protocols, various recording modes are available to further refine the resulting script. When recording web activity, HP LoadRunner allows a user to choose one of three types of recording modes: GUI based, URL based and HTML based.[10]

Parameterization

HP LoadRunner allows users editing a script with VuGen to replace recorded values in a script with parameters. This is called parameterization.[11]

Parameterization is often used:

When the application needs

  1. Unique data (such as user name)
  2. Data dependency (such as passwords)
  3. Data cache
  4. Date constraint

Correlation

HP LoadRunner uses Correlation to handle dynamic content. Dynamic content refers to page components that are dynamically created during the execution of a business process, and the value may differ from the value generated in a previous run. Examples of dynamic content include the ticket number in an on-line reservation system, a transaction ID in an on-line banking application and most importantly the unique session ID that is created each time a user logs in. Such dynamic values must be correlated in order to run the recorded script. The script while running will return an error if such a dynamic value has not been correlated, since the value changes each time the user logs in.

If the dynamic content is a part of a previous server response, LoadRunner can correlate that value with future instances in which it must be sent back to the server. HP LoadRunner saves the changing values into parameters, which are used during simulation.[12]

Controller

Once a script is prepared in VuGen, it runs using the LoadRunner Controller.[13] The Controller manages and maintains the scenarios that are run. During a scenario run, the Controller allows monitoring of network and server resources. The Controller assigns virtual users and load generators to specific scenarios.[14]

Load Generator

Multiple machines can be set up to act as load generators in concert. For example, to run a test of 1000 users, three or more machines can be set up with an HP LoadRunner agent installed on them. These machines are known as load generators because the actual load is generated from them. Each run is configured with a scenario that describes which scripts will run, when they will run, how many virtual users will run, and which load generators will be used for each script. The tester connects each script in the scenario to the name of a machine that is going to act as a load generator and sets the number of virtual users to be run from that load generator.This is called the working in HP load runner.[15] HP LoadRunner can control multiple load generators and collect results, and it can control load generators located at remote networks (through a firewall) if required.[16]

Analysis

The Analysis tool takes the result from the completed scenario and prepares graphs and reports that are used to correlate system information and identify bottlenecks and performance issues.[17] All the graphs that contain data that may affect response time, for example, can be merged for a better understanding of the performance and to pinpoint performance problems. Once all the graphs are adjusted, an HP Load Runner report can be prepared, including related graphs, in HTML or Microsoft Word format.[18]

HP LoadRunner in the Cloud

In May 2010, HP announced that an on-demand version of the application performance testing software would be available via Amazon Elastic Compute Cloud.[19] HP LoadRunner in the Cloud is first being offered as beta software in the U.S. and is available with pay-as-you-go pricing. The software is intended for performance testing for businesses of any size.[20] HP LoadRunner in the Cloud is part of a portfolio of cloud computing solutions offered by HP Software Division.[21]

Product Versions

LoadRunner Version History Control:

  1. Version 11.0 Patch 4 (Nov 2011, HP SV (Service Virtualization Integration) with Controller, GWT-DFE(Google Web Toolkit- Data Format Extension), RTMP Tunneled, Messaging support, Streaming support, Flex Correlations)
  2. Version 11.0 Patch 3 (06/20/2011, IE9 support, added two Mobile protocols, added support for GraniteDS)
  3. Version 11.0 Patch 2 (02/22/2011, support for Visual Studio 2010 and Protocol Updates to Ajax TruClient, Citrix, Flex, Web)
  4. Version 11.0 Patch 1 (01/06/2011)
  5. Version 11.0 available September 2010
  6. Version 9.52 patch to 9.51 (06/14/2010, a clean installation of 9.50 must first be upgraded to 9.51, and then to 9.52)
  7. Version 9.51 patch to 9.50 (file KM750376 file LR_03009.zip, dated July 6, 2009, is a 201 MB zip. enables better AJAX recognition and specification of DOM element properties. This runs GACSetup.exe and Magentconfig.exe, which require Vista users to allow)
  8. Version 9.50 available June 2009
  9. Version 9.10 installer, available Feb. 2008, is 2.31 GB after expansion. However, the folder created after an English language install is 931MB.
  10. Version 8.0 became available August 2004. It adds "Additional Attributes" to Runtime Settings. It also adds (for additional fee) diagnostics and tuning capabilities, allowing Transaction Breakdown to break down transaction times across different servers servicing various transaction layers (web server, Oracle 11i & Peoplesoft 8 app server, database) layers. It separates SQL time in execute, parse, and fetch times.
  11. Version 7.8 Feature Pack 1 added support for Windows XP.
  12. Version 7.8 became available September 2003.
  13. Version 6.5 available June 2000 offered new "TurboLoad" technology — a completely new replay engine that runs thousands of VUsers on a single load generator. Every VUser utilised a single operating system thread, while 50 VUsers ran in a single process by default.
  14. Version 6.0 used a separate process per user, which required almost 10 times more i/o and CPU cycles than 6.5.

References

  1. ^ HP LoadRunner software data sheet
  2. ^ “HP Closes Landmark Mercury Acquisition” news release.
  3. ^ Cnet.com “HP LoadRunner 9.5.” Retrieved 2010-03-05.
  4. ^ Exforsys Inc. “Why Choose LoadRunner for Performance testing.” Retrieved 2010-03-05.
  5. ^ “Virtual User Generator and Vuser scripts.” Retrieved 2010-03-05.
  6. ^ Software QA. “Working with VuGen Defining Parameters.” Retrieved 2010-03-05.
  7. ^ Atoz-performancetesting.com. “Comparison of features of Loadrunner, Silk Performer and RPT.”
  8. ^ “How Do We Record An Application Using HP LoadRunner?” Retrieved 2010-03-05.
  9. ^ WilsonMar.com. “www.VuScripting.info for LoadRunner.
  10. ^ “URL vs HTML recording mode.” Retrieved 2010-03-05.
  11. ^ Scribd. “LoadRunner-Parameters Chapter 7.” Retrieved 2010-03-05.
  12. ^ “LoadRunner Presentation.” Retrieved 2010-03-05.[dead link‍]
  13. ^ "LoadRunner Controller."
  14. ^ “LoadRunner Concept and Presentation.” Retrieved 2010-03-04.
  15. ^ "Fundamentals of LoadRunner."
  16. ^ Atoz-performancetesting.com. “Comparison of features of LoadRunner, Silk Performer and RPT.” Retrieved 2010-03-04.
  17. ^ “Load Runner Analysis Presentation.” Retrieved 2010-03-08.
  18. ^ “HP Load Runner Tutorial.” Retrieved 2010-03-04.
  19. ^ CTO Edge: “HP Puts LoadRunner on Amazon Cloud.” May 2010.
  20. ^ HP.com news release: "HP ten.to.one Initiative Fuels Growth, Reduces Complexity." May 2010
  21. ^ IDG News Service: Infoworld.com. “HP to launch enterprise cloud service.” Jackson. January 201
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=LoadRunner&oldid=480816665"