The latest release of k6 is...not v1.0, but an intermediate release preparing for some upcoming bigger changes that we want to get into k6 before we cut a v1.0 release. There are however some interesting additions, and bug fixes, in this release:
v0.21.0 is here! 🎉
We're happy to see continued contributions from members of the community in this release, from 4 people outside of Load Impact this time around. A big thanks to the following people for contributing to this release: @antekresic, @cyberw, @danron and @jmccann. Also, thanks to everyone that contributed in other ways on Github, in Slack and for spreading the word about k6!
This article takes a look at the k6 pause/resume/scale/stats/status commands, and how to use them to control and query a remote k6 instance running a test. This can be useful when you want to dynamically control a load test at runtime, pausing it or modifying the number of virtual users.
Lots of goodies in this release! 🎉
We are working towards a 1.0 release of k6, and as part of this release we've also published our roadmap for 2018 in the Github wiki. We welcome comments and discussion relating to the roadmap, both in the corresponding issues as well as in Slack.
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.
Are you on the lookout for a load testing tool, but fear the time investment you’re going to have to make to install, configure and then evaluate a bunch of different tools?
(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).