Join our webinar where we'll cover the basics of load testing and how to build an automation pipeline using Jenkins executing tests on LoadImpact.com. In the end we will also take a peak view on our next major platform upgrade, built on top of our open source load testing tool - k6
A good year!
Just now we released k6 version 0.18, which includes substantial changes from 0.17. I wanted to tell you a bit about those, and also look back at what has happened in the project during 2017.
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.
Mobile testing is hard. But with today’s application architectures, load testing can address many of the important bottlenecks in your overall app or browser performance. First, though, let’s look at user behavior.
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.
Many businesses run on a calendar fiscal year. And even those that don’t often budget quarterly. No matter how your business is organized, you’re likely looking at getting some spending done before the end of the quarter. Here are a few ideas based on our experience in optimizing performance.
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.
|Load Impact’s Insights allows you to stream the results of your local k6 test run to Load Impact’s cloud services. You can then view and analyze the result in the web browser. To do this you need a k6 cloud token (you can generate one from your Load Impact account when you join the insider program). You then run k6 locally with the -o cloud flag:
$ K6CLOUD_TOKEN=<your_token> k6 -o cloud script.js
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.