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.
Internet giants sometimes approach testing differently than the rest of the world should. For example, in a recent Bloomberg BusinessWeek article, Alibaba Cloud senior product manager He Yunfei talks about Singles Day as the ultimate load test, basically. “We use it as a drill. It sharpens us,” he says, according to the article.
As with people, regular checkups can ensure your site’s healthy performance. You’re more likely to find small issues before they become big problems when you consistently perform site performance checkups.
This month we have more updates to share around k6 (our new and open source load testing tool) and LoadImpact Insights. In the last product update email we mentioned we have some major improvements to our product in the works. To be more specific, we can now share with you that we’re building a new version of the LoadImpact product on top of k6 and with Insights as the result experience for k6 based tests. This means that k6 tests will get a new execution mode. Besides being executable locally on machines that you manage yourself, it will be possible to execute k6 tests on globally distributed infrastructure managed by us in the cloud. The result analysis for both modes of execution will be available through Insights.
We’d like to tell you that you can now rest easy: everything you’ve built will run just fine no matter how much traffic you get. Wouldn’t that feel nice? But the latest trend reports suggest that e-commerce growth shows no sign of slowing — and your consistent load testing and performance testing can help your site be ready.
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.
It’s one of our most commonly asked questions: what about CI integrations for performance testing? The short answer is simple: we have them, you should have them, and you should make sure you’ve implemented them.
Finally! Your site has hit the big time and your traffic is off the charts. Congratulations: is your site performance up to the task? Here’s a case where “be careful what you wish for” rings true: when that traffic rush hits, the best way to prevent disaster is with performance testing.
When should you plan for that traffic rush? Now. Start today.
As Viach Kakovskyi (@BackendandBBQ) stated in his blog post "If you do not have time to write tests today - you will find the time for fixing bugs Friday’s night". In other words, to establish solid reliability in production tomorrow we need to invest our time today.