Performance is a Feature It Should Be Tested as Such
summary
Claim: performance is a feature and must be tested with concrete assertions. Uses Blackfire plus the blackfireplayer and declarative blackfire.yaml scenarios to generate a profile for every page step, run in CI or as periodic builds (every six hours). Tests assert concrete numbers — e g wall time < 100 ms, < 50 Eloquent objects — rely on ~600 built‑in metrics, produce per‑step profiles, and surface failures immediately so automation actually catches regressions.
AI-written summary · about
chapters (9)
- 0:00Start
- 9:48A Database Connection Should Be Opened Only When Queries Are Made
- 15:55Scenarios
- 18:57Authentication
- 19:31Assertion
- 20:25Blackfireplayer
- 20:41Blackfire Player
- 25:07Periodic Builds
- 26:30Writing Scenarios
related talks
29mProgressive Testing to Meet the Performance Imperative
49mPerformance Testing
42mAdding Performance Assertion to Standard Functional Testing
38mPerformance 101
01h 00mPerformance In Modern Times: An Evolutionary Journey
12mPerformance In Context
39mCreating & Scaling Meaningful Performance Tests in CI
41mShift Left your Performance Testing