All Levels of Performance Testing and Monitoring in Web Apps
summary
How to design web-app performance testing and monitoring so business stakeholders’ non-numeric expectations ("fast", "lightning") are enforced across all tiers. The talk describes using OSS (ELK Stack) and commercial (AppDynamics) monitoring, integrating an appropriate load generator into the test automation ecosystem, and using the W3C WebDriver/Browser Timing APIs to collect timing data; it also recounts a case where matching monitoring data to Selenium/Allure test failures revealed environmental causes.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:18What is performance testing
- 2:43Performance in functional tests
- 4:05Timing API for metrics
- 6:11Business performance requirements
- 8:19Tech stack and app structure
- 10:05DB and server monitoring
- 11:51User experience monitoring
- 13:37JS agents in automated tests
- 16:52Data correlation and deep analysis
- 17:34Production statistics
- 18:37Gatling load testing intro
- 21:53Getting started with Gatling
- 25:43Global Assertions in Gatling
- 26:46Running tests from regions
- 27:49Performance tests in CI/CD
- 29:56Benefits of performance testing
- 31:00InfluxDB and Grafana integration
- 34:50Monitoring impact on performance
- 37:40Spike testing and issues
- 39:03Frontend/backend requirements
- 41:34Automated performance checks
- 44:27Correlation data analysis
- 45:13Swagger to Gatling tests
- 47:04Production testing setup
- 48:32Summary and Q&A
related talks
33mWeb App Performance Testing Using WebDriver
37mAutomated Performance Testing With WebDriver
01h 00mPerformance In Modern Times: An Evolutionary Journey
09mPerformance is the first UX challenge to consider
35mWeb Application Performance Testing from Users Perspective
43mThe one about Flashpoint or why the web needs speedsters
26mAutomated Web Performance Testing Before 5pm
29mProgressive Testing to Meet the Performance Imperative