The AST CASTcast: Episode 16: What the Heck do Performance Testers Really Do?
summary
Explains how performance testing recreates production throughput in preproduction using JMeter plus proprietary libraries and an in‑house proprietary analysis tool that captures per-second results. Describes the work: requirements hardening, mining legacy data, scripting automated scenarios, running baseline tests and iterating — for example a baseline that sustains 100 users but shows latency growth at 200 users, and negotiating testable nonfunctional goals like page loads within 2–5 seconds. Gives concrete tooling, data, and outcomes rather than abstract promises.
AI-written summary · about
chapters (10)
- 0:00Welcome to CASTcast
- 0:49Guests' origin stories
- 1:55Role of performance testers
- 3:20Recreating production load
- 4:25Performance testing misconceptions
- 5:26Automation in testing tools
- 6:32Negotiating requirements
- 7:59Empirical performance expectations
- 9:02Setting baselines and iterating
- 9:43Closing and contact
related talks
57mOpen Forum on Performance Testing
31mHow we can manage performance testing?
40mAutomated Performance Testing In Preproduction
29mProgressive Testing to Meet the Performance Imperative
41mMartijn Goossens: Become a Performance Test Master - the Non-Technical Side of Things
44mPerformance Testing: the way to make a true load
47mLee Barnes: Maximizing the Value of Performance Testing Throughout the Software Development Cycle
41mPerformance Testing — It's Simple (*)