Discovered a new term today, thanks to Lewis Prescott: Continuous Performance Testing.
"Performance testing kind of still follows that waterfall nature because it takes a long time to set up these scenarios and set up the environments, and it's expensive. So you don't wanna be doing all these things within the quality engineering kind of continuous model because it's gonna be very expensive and very time consuming. So that's where we come on to smoke scenarios...you're looking for trends. You run this today, then release and look at it tomorrow to see the difference. You're looking at a variation in the timing."
Lewis goes on to mention that this approach compliments the more traditional detail-driven types of performance testing such as load, volume, stress, soak, peak and spike.
I wonder who else is doing this. What does Continuous Performance Testing mean to you and how are you and your colleagues implementing it in a quality engineering context?
Look out for Lewis' talk during the Software Quality Engineering Certificate (SQEC) Module 6, Lesson 5: Performance testing in a quality engineering context.
