Integrating Taurus with Jenkins

Author: Iurii Bushnev

Welcome to part 3 of our “Continuous Functional and Performance Test Automation with Selenium, JMeter and Taurus” series. In the previous articles, we covered how to create Taurus scripts from scratch without direct use of Selenium and JMeter, and how to create and read reports on Taurus. In this article, we will go over how to integrate Taurus with Jenkins. In this article, we will explain how to put our Selenium and JMeter tests that are run by Taurus, in the Continuous Integration cycle.

Jenkins is the must-have solution for those who want to have free open source continuous integration server and control process of project build and tests execution on daily bases. You probably have Jenkins on your computer, but if you don’t, install it from here.

Jenkins usually runs under a default user called ‘Jenkins’. Since Taurus creates temporary data and also different reports, you might run into issues if Taurus doesn’t have writing permissions for its working directory.

Therefore, as a second step change the Jenkins default user. Here’s how:

Third, install the Jenkins Plot Plugin. It will be useful for comparing your basic performance metrics for the last builds. To install the plugin go to the ‘Manage Jenkins’ section and open the ‘Manage Plugins’ menu entry. Then, go to the ‘Available’ tab and find ‘Plot Plugin’ in the list below.

Now let’s move to building a plan creation. To configure Jenkins do the following:

In the build section run your YAML script:

You can also add post build action for plots creation. It is better to configure it this way, since the ‘timeStamp’ produces very large values and that makes its general graph user-unfriendly.

Add post build action for JUnit tests result statistic:

After the build execution, you will be able to see the tests results trend graph that is related to the JUnit tests report:

There is also an additional ‘Plots’ section on the left menu that provides you with the final Taurus statistics for a configurable number of builds.

At the same time, you can analyze all your metrics on CA BlazeMeter, for a detailed investigation of the product health, trends and KPI performance.

Congratulations! You now know how to run Taurus tests in the Continuous Integration cycle with Jenkins.

The Taurus team is open for feedbacks and suggestions and you can be sure that you will get help for any issues via the support forum.