Load Testing Strategy 101
- 1. Load Testing –Taking a Disciplined Approach Presented by: Ragan Shearing
- 2. Overview of PresentationWhy Load Test? How to Load Test? What is Load? What Kinds of Load Tests are There? What to Measure? How Are Requirements Set? What to include in the test? What do the Results Mean?
- 3. Why Load TestSame reason any testing is done, so we know what happens when ___________. Can be too expensive not to test. Identify the end user experience Tell customers what to expect from delivered software Identify whether change is good, bad or indifferent. Plan for capacity
- 4. How to LoadTest? Old Fashion Way Manual testers/users with stop watches Not efficient, very expensive Automated Tools Unit/Code Exercisers Communication Emulation/Simulation All mean to work the same way, induce a load on to a system
- 5. Question – Whatis Load? A load is any usage of a system A load begins with one One user, login, query One piece of functionality being exercised Logging out may be the end of the load, yet it induces load when executed
- 6. What Kinds ofLoad Testing is There? Different Load Tests are Defined by the Requirements or the Goal of the Test Effort. If the goal is ________ we run a _______ Endurance Test Long Term Stability Load Test System Capacity Performance Test Understand End User Experience
- 7. What to Measure?Overall system health during the test App, Web DB Servers CPU & Memory Utilization Connection Queue(s) Hard drive capacity 90 th Percentile of Transaction Response Times Percent Failures
- 8. What to Measure- continued Use the Above to Identify: Upper limit of users How system crashes and recovers Number of transactions Whether or not transaction responses stay steady or increase over time
- 9. How Are RequirementsSet? Understand the users, their usage and the business needs Report Tool vs Web Retailer Apply common sense and get sign off from the business When requirements are not, business either accepts the performance as is or… 5 second response time, user is content 5 second response time, user is very happy 30 second response, user goes to competitors site 30 second response time, user likely waits
- 10. What to includein the test? Core Application functionality Use 80/20 Rule Leave admin related processes out Understand the load profile Don’t try to mimic busiest hour Find limits Check limits against expected usage
- 11. What do theResults Mean? A good load test will show: Upper user limit End user experience Growth potential of the environment Whether or not the application/system will meet the needs of the business/users today and in future
- 12.