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.
We talk a lot about continuous and consistent load testing for your ongoing projects. (Continuous load testing means you integrate it into your continuous integration pipelines; consistent means you always do it.) What we don’t talk about as much is when you should be load testing your new projects - not your ongoing ones.
Let’s say you’re starting a new project. When is the right time to start load testing? And how can you build your project so it’s the most friendly to load testing? Here are a few tips.
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.
Prepare for your upcoming traffic peaks - like FIFA World Cup 2018
Is your site ready for peak traffic? How can you prepare for your upcoming traffic peaks? It’s more than just Black Friday and Cyber Monday for many businesses. In fact, one of the busiest traffic periods is coming up: FIFA World Cup 2018. (More about it later.)
No matter what’s coming your way, we want you to be planning for your peak traffic times. And we also recommend load testing.
If you’re not doing it already, load test now before these traffic peaks hit.
With the new k6 HAR converter, it is dead simple to use a browser to record a user session and then let k6 replay it in a load test. This article describes the HAR converter feature and how you can use it.
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.