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
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.
There’re a lot of things happening at Load Impact at the moment, and to make sure you’re up to date on what we’re up to, we’ll start sending product update emails and posting this on our blog, in the frequency range of once a month. As always we’ll continue to update the changelog as soon as features and bugfixes gets released.
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.
For an e-commerce site, performance is key, especially during peak traffic periods. We often talk about preparing for Black Friday and Cyber Monday as traffic peaks. But realistically, those days aren’t the only days where traffic peaks.
(Warning to readers: this article is long and rambling, like most articles by the same author)
Once upon a time, I wrote a very simple command-line load testing tool in C. I called it "myload", partly because it was written by, well...myself, and partly as an allusion to MySQL (this was back in the days when MySQL ruled and I had yet to start using PostgreSQL).
At Load Impact we believe in goal oriented and automated load testing. That's why we have built k6 to work smoothly in such environments, integrating nicely with tools like CircleCI, Jenkins and TeamCity. Now we can offer even more integrations such as AWS Codebuild, bash (*nix /MacOS) and PowerShell (Windows)
Whether you’re new to DevOps or an experienced hand, sometimes it’s a challenge to explain the difference between performance testing and performance tuning. It happens to us, too. Here’s how we describe understanding performance testing and performance tuning.
For the most accurate load test, best practices (and common sense) dictate that your testing environment be as close to real production and user behavior as possible. We get it, though! Best practices don’t necessarily reflect the challenge and rush of a real development pipeline. For example, if you’re like us, you likely have a much larger amount of data in your production environment than in your testing and staging environment. A detailed, extremely realistic testing database is nice, but perhaps not necessary. Let us explain.