29-12-2012, 03:19 PM
LOADRUNNER
[attachment=45807]
ABSTRACT
LOAD RUNNER
Load Runner is a Mercury Interactive Tool that predicts performance and behaviour of the system.By creating lots of load, you can see how the system reacts at peak levels or with simultaneous Users.To test the application and Load Runner emulates an environment where multiple users work concurrently. While the application is under load, Load Runner accurately measures and analyzes the system performance, and its functionality.
Load Runner is a performance and load testing product by Hewlett-Packard for examining system behavior and performance, while generating actual load. Load Runner 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. The results can then be analyzed in detail, to explore the reasons for particular behaviors. Load testing is to test that if the application works fine with the loads that result from large number of simultaneous users, transactions. Timing for both read and update transactions should be gathered to determine whether system functions are being performed in an acceptable timeframe. This should be done standalone and then in a multi user environment to determine the effect of multiple transactions.
INTRODUCTION:-
Load Runner is a performance and load testing product by Hewlett-Packard (since it acquired Mercury Interactive in November 2006) for examining system behavior and performance, while generating actual load. Load Runner 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). The results can then be analyzed in detail, to explore the reasons for particular behaviors.
• Load Runner is a Mercury Interactive Tool that predicts performance and behaviour of the system.
• By creating lots of load, you can see how the system reacts at peak levels or with simultaneous Users.
• To test the application, Load Runner emulates an environment where multiple users work concurrently. While the application is under load, Load Runner accurately measures and analyzes the system performance, and its functionality.
HP automated load tools.
Simulates load on an application and collects data using monitors.
Has 3 parts
–VuGen
–Controller
–Analysis
Tests an application under the anticipated usage volume for the environment. Used to determine whether a file meets an SLA under standard usage conditions. Uses a few machine to simulate a large volume of load. Only multi user/distributed applications can be load tested. Load testing is NOT a substitute for functional testing. Load testing is NOT Stress testing. Load testing is to test that if the application works fine with the loads that result from large number of simultaneous users, transactions and to determine whether it can handle peak usage periods. It depends upon through put i.e.
Throughput=N*T*D
N=no of concurrent user
T=time taken to load data
D=data load per each transaction
Timing for both read and update transactions should be gathered to determine whether system functions are being performed in an acceptable timeframe. This should be done standalone and then in a multi user environment to determine the effect of multiple transactions on the timing of a single transaction, to test the performance of the application in different load condition. Load is increased to break points after that it fails. How much load it is tolerate. We consider that as the data integrity affected, data transaction lost, as the server shut down, system shut down.
• Manual testing:
1) It is time consuming.
2) It is expensive.
3) It is very difficult to co-ordinate multiple user.
4) It is very complicated.
• Automation testing:
1) It is time saving.
2) It is not expensive.
3) LR CONTROLLER controls the entire v user from a single point.
4) It is not complicated.
Load Runner is an automated load testing tool that allows you to test your application before, during and after deployment. This course is designed to give you a firm foundation in basic load testing tasks. The following components of Load Runner – LR Controller and LR Analysis are used to plan for an effective load test. You will create and run load test scenarios using the LR Controller. The LR Analysis component is used to analyze load test results. You will learn to interpret Load Runner analysis graphs and achieve your load testing goals. All topics are support by hands-on labs designed to provide you with the knowledge necessary to load test your system using load runner. We perform load testing once we are done with interface (GUI) testing. Modern system architectures are large and complex. Whereas single user testing primarily on functionality and user interface of a system component, application testing focuses on performance and reliability of an entire system. For example, a typical application-testing scenario might depict 1000 users logging in simultaneously to a system. This gives rise to issues such as what is the response time of the system, does it crash, will it go with different software applications and platforms, can it hold so many hundreds and thousands of users, etc. This is when we set do load and performance testing.
[attachment=45807]
ABSTRACT
LOAD RUNNER
Load Runner is a Mercury Interactive Tool that predicts performance and behaviour of the system.By creating lots of load, you can see how the system reacts at peak levels or with simultaneous Users.To test the application and Load Runner emulates an environment where multiple users work concurrently. While the application is under load, Load Runner accurately measures and analyzes the system performance, and its functionality.
Load Runner is a performance and load testing product by Hewlett-Packard for examining system behavior and performance, while generating actual load. Load Runner 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. The results can then be analyzed in detail, to explore the reasons for particular behaviors. Load testing is to test that if the application works fine with the loads that result from large number of simultaneous users, transactions. Timing for both read and update transactions should be gathered to determine whether system functions are being performed in an acceptable timeframe. This should be done standalone and then in a multi user environment to determine the effect of multiple transactions.
INTRODUCTION:-
Load Runner is a performance and load testing product by Hewlett-Packard (since it acquired Mercury Interactive in November 2006) for examining system behavior and performance, while generating actual load. Load Runner 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). The results can then be analyzed in detail, to explore the reasons for particular behaviors.
• Load Runner is a Mercury Interactive Tool that predicts performance and behaviour of the system.
• By creating lots of load, you can see how the system reacts at peak levels or with simultaneous Users.
• To test the application, Load Runner emulates an environment where multiple users work concurrently. While the application is under load, Load Runner accurately measures and analyzes the system performance, and its functionality.
HP automated load tools.
Simulates load on an application and collects data using monitors.
Has 3 parts
–VuGen
–Controller
–Analysis
Tests an application under the anticipated usage volume for the environment. Used to determine whether a file meets an SLA under standard usage conditions. Uses a few machine to simulate a large volume of load. Only multi user/distributed applications can be load tested. Load testing is NOT a substitute for functional testing. Load testing is NOT Stress testing. Load testing is to test that if the application works fine with the loads that result from large number of simultaneous users, transactions and to determine whether it can handle peak usage periods. It depends upon through put i.e.
Throughput=N*T*D
N=no of concurrent user
T=time taken to load data
D=data load per each transaction
Timing for both read and update transactions should be gathered to determine whether system functions are being performed in an acceptable timeframe. This should be done standalone and then in a multi user environment to determine the effect of multiple transactions on the timing of a single transaction, to test the performance of the application in different load condition. Load is increased to break points after that it fails. How much load it is tolerate. We consider that as the data integrity affected, data transaction lost, as the server shut down, system shut down.
• Manual testing:
1) It is time consuming.
2) It is expensive.
3) It is very difficult to co-ordinate multiple user.
4) It is very complicated.
• Automation testing:
1) It is time saving.
2) It is not expensive.
3) LR CONTROLLER controls the entire v user from a single point.
4) It is not complicated.
Load Runner is an automated load testing tool that allows you to test your application before, during and after deployment. This course is designed to give you a firm foundation in basic load testing tasks. The following components of Load Runner – LR Controller and LR Analysis are used to plan for an effective load test. You will create and run load test scenarios using the LR Controller. The LR Analysis component is used to analyze load test results. You will learn to interpret Load Runner analysis graphs and achieve your load testing goals. All topics are support by hands-on labs designed to provide you with the knowledge necessary to load test your system using load runner. We perform load testing once we are done with interface (GUI) testing. Modern system architectures are large and complex. Whereas single user testing primarily on functionality and user interface of a system component, application testing focuses on performance and reliability of an entire system. For example, a typical application-testing scenario might depict 1000 users logging in simultaneously to a system. This gives rise to issues such as what is the response time of the system, does it crash, will it go with different software applications and platforms, can it hold so many hundreds and thousands of users, etc. This is when we set do load and performance testing.