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.
Load Impact integrates nicely with Jenkins, a leading continuous delivery and integration automation platform. Using our robust and extensible APIs you can integrate Load Impact’s world-leading performance testing platform into your automated Jenkins pipeline build and test process.
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.
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.
(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).
Most developers are extremely familiar with automated testing as part of their CI/CD pipelines. Continuous improvement and continuous delivery integrate unit testing as a matter of course.
But there’s another type of testing you *should* be doing, but most developers aren’t. Since we’re load testing experts, we’re sure you’ve already guessed our recommendation: add load testing to your automation pipelines.
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)
The secrets to an effective DevOps team are communication and collaboration. This is especially true in load testing.
The #1 best practice we recommend with your regular load testing is to set pass/fail triggers with your automated build processes. (We’ve talked about that elsewhere.) As part of those triggers, failure notifications should be set up in a shared communications channel.