This article describes how to build an external command-and-control UI for exploratory load testing with k6. The UI is written in Python and features some awesome ASCII graphics using the Python curses library.
As discussed in the earlier blog on Performance Testing in the Cloud, performance testing tools must fit into today's DevOps workflows. This means that they should support both local testing and cloud based testing. Local testing for developers, early in the dev cycle, and cloud based testing later in the cycle for running larger tests.
Let's take a deeper dive into the cloud based testing scenario.
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.
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).