Performance Testing in Agile and DevOps
summary
Claims concrete changes: add a JIRA checkbox for performance impact, run fast CI/CD baseline checks using 50th-percentile metrics, and keep a handful of large lab tests for architecture changes. Tools and integrations named include JMeter and Gatling, Jenkins pipelines, APMs like Dynatrace and Datadog, plus Elastic/Splunk for analysis. Real effects include a CDN misconfiguration brought the site down and a 30‑second wait bug; mitigation includes route test transactions in production and running Cyber Monday loads regularly to validate fixes.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:18Gopal Brugalette Performance Architect
- 1:22Performance Engineering in Waterfall
- 2:14Performance testing challenges
- 3:11Perf as Non-Functional Requirement
- 3:39Performance as a Feature
- 4:49Responsibility for Performance
- 5:23Business & Marketing
- 7:00Planning and Requirements
- 8:57Performance in Agile Process
- 16:37Build a framework
- 17:30Lab Load/Stress Testing
- 18:50Test in Production
- 21:20Monitoring
- 23:11Agile Performance Engineering
- 23:53When Scrum?
- 24:44Kanban for Performance
- 26:13Swarming & Mobbing
- 28:09Build a DevOps Team
- 30:17Keep Score
- 30:42Target the right teams
- 31:55Whitepapers and Case Studies
- 32:53Performance is a Feature
related talks
41mPerformance Engineering in the Age of DevOps and Agile
41mContinuous Performance Testing in DevOps
44mContinuous Performance Testing in DevOps
40mAutomated Performance Testing In Preproduction
46mA Practical Guide to Testing in DevOps
50mMesut Gunes: Shift Left, Test Right: The Art of Continuous Performance Testing
40mWhy component level performance testing should always be part of CD and CI
26mThe Impact of Testing on a DevOps Pipeline