Skip to main content

Automated Performance Testing with K6

Automated testing is running the tests and reporting results by tools with scripts. Automated performance testing is designing the performance test scenarios to run them spontaneously by tools and evaluating the result by tools to decide to go or not to go further.

Automated Performance Testing is

  • A subset of the performance test scenarios
  • Designed to run spontaneously by tools
  • Designed to evaluate the result by tools
  • Designed not to break the system
  • Having decision metrics, ex: max response time, max-average resp time, ...
  • Designed to create reports for the concurrent and historical run

What Types of Performance Testing Should be Automated


Automated performance testing can be applied to all types of performance testing. However, each type needs a different level of maturity and sanity.

Automated Performance Testing is

  • Easily applied to load testing
  • Hard to apply stress test, spike test, but have benefits
  • Very hard to apply Soak-Endurance test

Automated Load Tests

Since the load test is aiming to the response of the system under a specific load and it is a success belongs to the pre-defined metrics, load testing is the best-suited performance testing type.

Automated Load Testing is
  • Needing a specific load level
  • Needing pre-defined metrics
  • Needing evaluation of the result
  • Needing exactly the same environment - only one thing can be testable
  • Needing tools and script knowledge
  • Easy to integrate CI/CD pipeline - everything is scripted
  • Reporting the performance of the system when something changes

Tools Needed for Automated Performance Testing


Performance testing depends on two main parts. The first part is creating loads and the second part is using these loads for test scenarios. When it comes to doing automated performance testing, we need more tools


Tools Needed for Automated Performance Testing are

  • Performance Testing tools
    • Open-source
      • Jmeter - Apache project, v1.0 1998
      • Gatling - Enterprise support by Frontline
      • K6 - Enterprise support by LoadImpact
      • Locust
      • and many others
    • Commercial
      • LoadRunner by Microfocus (previously Mercury - HP)
      • Blazemeter - support multiple opensource tools
      • LoadUI Pro by Smartbear
  • Databases
    • InfluxDB - Opensourced times series database
    • MongoDB - Opensourced document-based database
  • Reporting tools
    • Grafana
    • Kibana
    • Graphite
  • Orchestration Tools
    • Docker Compose
    • Kubernetes
    • Prometheus
    • Mesosphere DC/OS
    • And others
  • Automation Tools
    • And others
    • Jenkins
    • TravisCI
    • TeamCity
    • CircleCI
    • Code Ship
    • Gitlab CI"

A Way of Implementation of K6 for Automated Performance Testing

k6 Load Testing ResultsK6 is an open-source performance testing tool. It is designed for developers, it gives us many good features to run tests in a safer, faster, easier integrated way. Very easy to integrate it to CI/CD.

Some of the Good Features of K6 are
  • Precious in performance, among the top 5 in comparison
  • Written in Golang, allows writing test script in Javascript
  • Already dockerized
  • Easy to connect to DB (such as InfluxDB)
  • Easy to create reports (Grafana)
  • Has build-in Thresholds
  • And many others
K6 has rich libraries that you can use in the script. The request is sending by HTTP from k6/http. Grouping is letting you run the same kind of request in a group. Check the simple test scripts which have get requests to the three URLs and post requests to register endpoint with dynamic data. 


Command-line supports many parameters to run your scripts. For a load test, we have fixed virtual user and fixed test duration so the run script should look like


For a spike test, we should load the system with a nominal load and the load should increase suddenly. Let’s focus on at the --stage option for this.


K6 can be easily integrated with an InfluxDB instance so in the setup we are also running the docker-compose to create an InfluxDB instance with will use for feeding Grafana dashboard to visualize all the data.


The K6 sends the results to the InfluxDB, we can virtualize this data with Grafana. You can use the dashboard created by the LoadImpact


Add these scripts to your CI/CD pipeline to run an automated performance test and see the result in Jenkins. To see all the scripts and data check this repo on Github



Popular posts for software testing and automation

Selenium Error "Element is not currently interactable and may not be manipulated"

Selenium webdriver can drive different browsers like as Firefox, Chrome or Internet Explorer. These browsers actually cover the majority of internet users, so testing these browsers possibly covers the 90% of the internet users. However, there is no guaranty that the same automation scripts can work without a failure on these three browsers. For this reason, automation code should be error-prone for the browsers you want to cover. The following error is caught when the test script run for Chrome and Internet Explorer, but surprisingly there is no error for the Firefox. Selenium gives an error like below: Traceback (most recent call last):   File "D:\workspace\sample_project\sample_run.py", line 10, in <module>     m.login()   File "D:\workspace\ sample_project \test_case_imps.py", line 335, in login     driver.find_element_by_id("id_username").clear()   File "C:\Python27\lib\site-packages\selenium-2.35.0-py2.7.egg\selenium\webdriver\r

Change Default Timeout and Wait Time of Capybara

One of the biggest challenge for automation is handling timeout problem. Most of the time, timeout is 60 seconds but it may sometimes not enough if you have badly designed asynchronous calls or the third party ajax calls. This makes handling timeout more complex. set large enough to tolerate network related problems. For Selenium based automation frameworks, like Capybara, default Webdriver timeout is set to Net::ReadTimeout (Net::ReadTimeout) Changing ReadTimeout If you have timeout problem for Capybara, it gives an error like above. This means that the page is not fully loaded in given timeout period. Even you can see that page is loaded correctly but webdriver wait until the Ajax calls finish. class BufferedIO #:nodoc: internal use only def initialize (io) @io = io @read_timeout = 60 @continue_timeout = nil @debug_output = nil @rbuf = '' end . . . . . def rbuf_fill beg

Page-Object Pattern for Selenium Test Automation with Python

Page-object model is a pattern that you can apply it to develop efficient automation framework. With the page-model, it is possible to minimize maintenance cost. Basically page-object means that your every page is inherited from a base class which includes basic functionalities for every page. If you have some new functionalities that every page should have, you can simple add it to the base class. Base class is like the following: In this part we are creating pages which are inherited from base page. Every page has its own functionalities written as python functions. Some functions return to a new page, it means that these functions leave the current page and produce a new page. You should write as much as functions you need in the assertion part because this is the only part you can use the webdriver functions to interact with web pages . This part can be evaluate as providing data to assertion part.   The last part is related to asserting your test cases against to the

Create an Alias for Interactive Console Work: Selenium and Capybara

If you are working on shell most of the time Aliases are very helpfull and time saving. For testing purposes you can use Alias for getting ready your test suites. In this post, I want to explain both running Selenium and Capybara on console and creating aliases for each.  This post is for Windows machines, if you are using Unix-like see   this post . Creating Scripts for Selenium and Capybara First of all, it is assumed that you have installed Selenium and Capybara correctly and they work on your machines. If you haven't installed, you can see my previous posts. I am using the Selenium with Python and the Capybara with Ruby. You can use several different language for Selenium but Capybara works only with Ruby.  Create scripts in a directory called scripts (in your home folder, like as  ~/scripts ) for your automation tool as following, save them as capybara.rb, sel.py :  Creating Aliases Depends on your favourite shell, you need to add the alias to .bashrc bash

Performance Testing on CI: Locust is running on Jenkins

For a successful Continuous Integration pipeline, there should be jobs for testing the performance of the application. It is necessary if the application is still performing well. Generally performance testing is thought as kinds of activities performed one step before going to live. In general approach it is true but don't forget to test your application's performance as soon as there is an testable software, such as an api end point, functions, and etc. For CI it is a good approach to testing performance after functional testing and just before the deployment of next stage. In this post, I want to share some info about Jenkins and Locust. In my previous post you can find some information about Locust and Jenkins. Jenkins operates the CI environment and Locust is a tool for performance testing. To run the Locust on Jenkins you need command line arguments which control the number of clients ,   hatch rate,  running locust without web interface and there should be so