Ciprian balea automated performance-testing
0 likes1,433 views
This document discusses automated performance testing for desktop applications. It outlines challenges like inconsistent loading times and accessing system resources without third-party tools. It then describes a testing process to address these challenges. The process automatically runs a test sequence 1000 times to collect webpage loading times, CPU/memory usage, and disk I/O. This helps predict real-world performance and identify needed improvements. Results are saved to Excel for analysis. In conclusions, automated performance testing requires initial effort but provides very conclusive results to boost an application's performance.
Ciprian balea automated performance-testing
- 1. D I S C I P L I N E D I N N O VAT I O N AUTOMATED PERFORMANCE TESTING FOR DESKTOP APPLICATIONS CIPRIAN BALEA
- 2. THE SCARY QUESTION OF APPLICATION DEVELOPMENT How does it perform in real life conditions? Never as first expected!
- 3. BENCHMARKING Ideally: • consumming as little resources as possible without loosing functionality • the app should not break / slow the system down What impact does the app have on the system running it? (is the system still reliable) How does the app perform when running on the host system? (does it keep all functionality)
- 4. HOW TO PREDICT THE FUTURE? Run it multiple times, and average out. A slingle run doesn’t acurately predict real life usage.
- 5. HOW TO GET A CREDIBLE RESULT Avoid inconsistencies induced by the outside world => no Internet connection, own webserver & assets
- 6. WHAT’S OUR APPLICATION ABOUT A custom web browser
- 7. HARDWARE SETUP © Copyright 2013 3PILLAR GLOBAL All rights reserved 7
- 8. BIG PROBLEM #1: HOW TO KNOW HOW MUCH THE PAGE TOOK TO LOAD Small solution: Based on the HTML content, loading time cannot be computed. (element loading order is not consistent across multiple runs)
- 9. BIG PROBLEM #2: HOW TO READ SYSTEM RESOURCE USAGE WITHOUT 3RD PARY TOOLS Small solution (a):
- 10. BIG PROBLEM #2: HOW TO READ SYSTEM RESOURCE USAGE WITHOUT 3RD PARY TOOLS Small solution (b)
- 11. BIG PROBLEM #3: HOW TO MANIPULATE THE APPLICATION’S GUI Small solution:
- 12. WHAT DATA WE COLLECT Test 1 • Webpage load time • CPU usage • Memory usage • Disk I/O Test 2 • Timing a „complex” operation
- 13. TEST 1: READING SYSTEM STATISTICS
- 14. HOW IS THE DATA COLLECTED Not at the start of the game Not at the end of the game Throughout the entire game
- 15. HOW IS THE DATA COLLECTED
- 16. RUNNING THE TEST One test sequence: • clear cache • open the browser • start reading system data • load webpage • close the browser • save result in an Excel spreadsheet Full test: • restore the “clean” snapshot of the test environment • automatically run the test sequence for 1000 times on the native browser • automatically run the the test sequence for 1000 times on the custom browser
- 17. RUNNING THE TEST
- 18. TEST 2: TIMING A „COMPLEX” OPERATION
- 19. „COMPLEX” OPERATION Open the browser Load a webpage Bookmark page Go to homepage Open bookmark Wait for page to load
- 20. RESULTS
- 21. RESULTS
- 22. CONCLUSIONS It can be automated with an initial effor, but the returned value is huge. Offers very concludent results on what needs to be improved in the application to boost performance. Performance testing is very important as it can reveal performance flaws. Is very time & effor consuming to do manually.
- 23. Q & A
- 24. THANK YOU !