The shift in development styles to rapid deployment (rapid app development) has been great in many ways for developers, for devops and for business. You’re likely implementing continuous integration and continuous delivery in as many places as you can. Or your CI/CD imperatives have come down from management.
You’re committed to load testing because you’re convinced of its benefits. But are you load testing both consistently and continuously?
Both are important, and both deliver results. Those results not only optimize your app’s performance - but can catch job-threatening performance issues early in development. Let’s talk about them individually.
We recently talked about the “new” shift left testing trend. The concept is important, for sure, especially in a larger, less nimble development organization. But all testing, we believe, should be developer-first.
The phrase “shift left” testing has gained some recent traction. But what does “shift left” mean for you? In short, it means what you already know: the earlier you test, the better, and you should test consistently and continuously.
We’re in the thick of the heaviest traffic season for many sites and apps. Autumn through the end of the year often brings major traffic spikes, be they from Singles Day, Black Friday, or other seasonal retail peaks. But no matter when your site’s traffic peaks, there’s one big pitfall you need to avoid:
Don’t stop testing after your peak traffic period.