1 / 25

Structured Load Tests for Web Applications

In the presentation by Martin Lugan, a Test Engineer at Haufe-Lexware, the significance of structured Performance, Load, and Stress (PLS) testing in application lifecycle management is explored. Key topics include the types of tests, requirements for structured testing, planning, execution, assessment of results, and validation of test reports. The presentation emphasizes best practices, challenges faced in resource management, and the importance of accurate configuration and monitoring to ensure realistic outcomes.

ayoka
Download Presentation

Structured Load Tests for Web Applications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Structured Load Tests for Web Applications Martin Lugan QC Engineering Team Status: 20.06.2013

  2. Speaker • Martin Lugan is a Test Engineer in the Quality Control domain at Haufe-Lexware in Freiburg • He is responsible for topics such as PLS tests, test environment virtualisation and test data anonymisation . • Contact information: • Martin Lugan • Haufe-Lexware GmbH & Co. KG • Munzinger Str. 9 • 79111 Freiburg • Telephone +49 761 898-5209 • E-Mail Martin.Lugan@haufe-lexware.com • Web http://www.haufe-lexware.com/

  3. Introduction

  4. Agenda • Why do we carry out structured Performance, Load and Stress tests (PLS) • The Test Types for PLS Tests • Requirements for Structured Performance and Load Tests • Test Planning: Mandatory information and risks • Test Execution • Result Assessment • Test Reports and Validation • Appendix

  5. Why do we carry out structured Performance, Load and Stress tests?

  6. What are the advantages of Load Tests?

  7. Performance Management in Application Lifecycle Management (ALM) Test types and test environment design Definition of non-functional requirements (Performance) Lab and module test Performance (End2End) Monitoring Performance, Load and Stress test according to demand

  8. Requirements for Structured Performance and Load Tests

  9. PLS Test Types:Performance Test / Stress Test

  10. PLS test types fail-over / scalability load test <-Fail ->

  11. PLS test types:Continuous Load Test

  12. Tools

  13. Example for the Content of a Test Plan

  14. Script creation and the test environment

  15. Test Execution:

  16. Overload • Stability • Elasticity Typical response time wave

  17. Results Assessment - Successful test run • Even for an ever-increasing load generated by an increasing number of virtual users, the response times will only grow marginally. • However, the individual transactions with strongly differing response times are not satisfactory.

  18. Results Assessment - Typical resource problem from the server side • The increasing number of vUsers means longer response times.

  19. Results assessment - further errors In this test, the load was raised in the first hour. Afterwards, the load remained the same. After 1:30, we can see a significant drop in the load times. The cause was an incorrectly configured caching of database accesses.

  20. Results Assessment - further errors • In this test run, the DB connections were not closed by the application (see monitoring graph above - test run starting at 12:30). The result is, that after reaching the configured maximum DB connections, the server had to be restarted twice.

  21. Monitoring

  22. Test Report

  23. Validation • In order to check if the tests have delivered realistic and meaningful results, a validation of results should be done. • e.g. by comparing the resource load on the test and live system. • Do we encounter load or performance problems in the live system that we did not encounter in the test execution? <- CPU Load Test system <- CPU Load Test system on a normal Monday morning

  24. Appendix • References: • The slides 6, 17 were taken from „PLS-Roadshow” – Markus Lobreyer & Pandora Project • Translation into English: Victor Giurgiu

  25. Performance Management Maturity Model (Maturity Levels)

More Related