Mesut Gunes: Shift Left, Test Right: The Art of Continuous Performance Testing
summary
Continuous Performance Testing becomes part of CI/CD, running per-commit k6 load tests (JMeter, Gatling, Locust as alternatives), pushing results into a database and APM for comparison against a 95% confidence baseline derived from historical runs; static p95 and max gates also work. Stress and spike tests are useful but risky and expensive to run in CI. Target automated feedback within a 5-minute CI budget for load checks, use longer endurance runs offline, and consider AI/statistics to flag regressions.
AI-written summary · about
chapters (8)
- 0:00Performance issues in production
- 3:40What is performance testing
- 10:05Types of performance testing
- 22:43Continuous testing in CI/CD
- 27:28Performance metrics and evaluation
- 36:54Tools for continuous testing
- 39:50Benefits of continuous testing
- 40:32Q&A
related talks
33mPerformance Testing in Agile and DevOps
40mAutomated Performance Testing In Preproduction
41mContinuous Performance Testing in DevOps
44mContinuous Performance Testing in DevOps
34mWhy continuous testing is essential
53mEarly Performance Testing: Finding News You Can Use
16mWhy is Continuous Testing Important?
44mStrategy for Acing Continuous Testing in DevOps