1. Session on Load Testing - Alok Agarwal

2. Agenda for the session Definitions Example on load testing What to Avoid When Testing for Load Goals of Load Testing Test Plan for Load Testing a web Application Demo on LoadRunner tool

3. Definitions

4. Performance Testing Identify tasks and measure how long it takes to do each task It will specifically refer to response times

5. Load Testing Load testing will include the applications behavior up to and including its limits. Load testing refers to steady increases in load until significant operational degradation or failure. This will specifically refer to the load size (number of virtual users) and related values.

6. Stress Testing Study the program's response to peak bursts of activity

7. Example for Load Testing

8. Performance Testing The automobile does zero to sixty miles per hour in a certain number of seconds under various conditions

9. Load Testing The automobile can pull a trailer weighing a certain number of tons before it can no longer move

10. Stress Testing The automobile continues to work fine driving 60 miles an hour for two hours, in 120 degree temperatures, with only a gallon of fluid in radiator

11. What to Avoid When Testing for Load

12. performing load tests on applications that are changing even as the tests are being performed performing load tests with applications that are not functionally tested so that even basic capabilities are not operational

13. performing load tests on certain parts of the application that work and extrapolating the results to the entire application performing load tests with a smaller number of concurrent users and extrapolating the result for larger numbers

14. Goals of Load Testing

15. Determine the ”Magic Number" The magic number is the maximum number of concurrent users that the system can support while remaining stable and providing reasonable response time to users as they perform a variety of typical business transactions

16. Determine end user experience under load Can users get to the Web application in a timely manner? Are users able to conduct business or perform a transaction within an acceptable time? What is the failure rate that users observe? Is it within acceptable limits?

17. Determine server-side robustness and degradation Does my Web server crash under heavy load? Does my application server crash under heavy load? Does my database server crash under heavy load? Should hardware changes be made for improved performance?

18. Test Plan for Load Testing a Web Application

19. Define a process that is repeatable for executing load tests throughout the application life-cycle Define the criteria for load test Determine the software tools required to run the load test Determine and configure the hardware and environment needed to execute the load tests

20. Plan the load tests Plan the test scenarios Create and verify the Visual Scripts Create and verify the load test scenarios

21. Execute the tests Evaluate the results against the defined criteria Generate required reports

22. Thank you by Sumanth