Progressive Testing to Meet the Performance Imperative
summary
Claims that baking performance criteria into stories cuts production problems by about half as many problems, shows tooling used end to end with concrete wins, and advocates API performance and security testing early rather than vague examples. Demonstrations include using dynaTrace under synthetic load for real time visibility, reworking Selenium Grid visibility, dynamic provisioning of test environments in CI (Jenkins/Circle) and a rule of thumb to stop if servers hit ~80% capacity.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:49Pauls background
- 2:25Idea generation
- 2:38Collaboration
- 3:25Open Spaces
- 4:23Software Engineering
- 6:16Performance Imperative
- 7:27Availability
- 7:58Performance
- 9:37Empathy
- 10:52User Experience
- 11:54Developer Experience
- 12:06Downstream Rework
- 13:05Commit
- 14:05Bake
- 14:41Broken code
- 15:19Feedback
- 16:44Time Budget
- 18:07Micronizing
- 18:55Failure Budget
- 20:39Confidence
- 22:29Site Reliability
- 25:01Dynamic Provisioning
- 27:36Wrap Up
- 28:49Thank You
related talks
41mPerformance Engineering in the Age of DevOps and Agile
41mContinuous Performance Testing in DevOps
01h 00mPerformance In Modern Times: An Evolutionary Journey
40mAutomated Performance Testing In Preproduction
44mContinuous Performance Testing in DevOps
53mEarly Performance Testing: Finding News You Can Use
57mOpen Forum on Performance Testing
50mCreating Performance Impact in a Changing Tech Landscape