Sei sulla pagina 1di 2

Why Choose LoadRunner for Performance testing

This article start with brief introduction to Performance Testing, Why should you automate performance testing, What are the LoadRunner components, LoadRunner Terminology and Load Testing Process.

Performance testing

Introduction
Performance Testing is the process by which software is tested and tuned with the intent of realizing the required performance. The performance testing part of performance engineering encompasses what's commonly referred to as load, spi e, and stress testing, as well as !alidating system performance. Performance can be classified into three main categories" # Speed $ %oes the application respond quic ly enough for the intended users& # Scalability $ Will the application handle the e'pected user load and beyond& # Stability $ (s the application stable under e'pected and une'pected user loads&

Why should you automate performance testing?


) well*constructed performance test answers questions such as" # %oes the application respond quic ly enough for the intended users& # Will the application handle the e'pected user load and beyond& # Will the application handle the number of transactions required by the business& # (s the application stable under e'pected and une'pected user loads& +y answering these questions, automated performance testing quantifies the impact of a change in business terms. This in turn ma es clear the ris s of deployment. )n effecti!e automated performance testing process helps you to ma e more informed release decisions, and pre!ents system downtime and a!ailability problems.

What are the LoadRunner components?


LoadRunner contains the following components: # The ,irtual -ser .enerator captures end*user business processes and creates an automated performance testing script, also nown as a !irtual user script. # The /ontroller organizes, dri!es, manages, and monitors the load test. # The Load .enerators create the load by running !irtual users. # The )nalysis helps you !iew, dissect, and compare the performance results. # The Launcher pro!ides a single point of access for all of the LoadRunner components.

LoadRunner Terminology
) scenario is a file that defines the e!ents that occur during each testing session, based on performance requirements. (n the scenario, LoadRunner replaces human users with !irtual users or ,users. ,users emulate the actions of human users wor ing with your application. ) scenario can contain tens, hundreds, or e!en thousands of

,users. The actions that a ,user performs during the scenario are described in a ,user script. To measure the performance of the ser!er, you define transactions. ) transaction represents end*user business processes that you are interested in measuring.

Load Testing Process


Load testing typically consists of fi!e phases" planning, script creation, scenario definition, scenario e'ecution, and results analysis. Plan Load Test: %efine your performance testing requirements, for e'ample, number of concurrent users, typical business processes and required response times. Create user Scripts: /apture the end*user acti!ities into automated scripts. !efine a Scenario: -se the LoadRunner /ontroller to set up the load test en!ironment. Run a Scenario: %ri!e, manage, and monitor the load test from the LoadRunner /ontroller. "naly#e the Results: -se LoadRunner )nalysis to create graphs and reports, and e!aluate the performance.

Conclusion:
Load Runner has good reporting features with which the user can easily analyze the performance test results.

Potrebbero piacerti anche