pylint and lxml

If you use Python virtualenv, pylint and lxml together, you may see error messages in pylint test results. It`s because only trusted C extension resources (the standard library) should be used. Here is an opportunity to improve the pylint test results.

Generate a .pylintrc file

Open the .pylintrc file for edit

Add lxml to extension-pkg-whitelist

If you now perform the pylint test again, no error relating to lxml should appear.

JMeter and Taurus

Taurus from Blazemeter seems really to have a potential to be a star. There are new and easy ways to ease the workflow with JMeter. It allows, for example, configuration options and reports which JMeter does not offer by default.


On error look for installed libxml2 and libxslt libraries!


You don`t need jMeter or jMeter PlugIns installed! All will automatically downloaded in given path (see YAML).


Create a JMeter testplan with “User Defined Variables”, one “Thread” with one “HTTP Request Defaults” and some “HTTP Requests”.

Taurus jMeter Example 1

On “User Defined Variables” – “Name” insert “MY_TARGET_HOST” this value will be set by Taurus YAML file.

Taurus jMeter Example 2

On “HTTP Request Defaults” – “WebServer” use the variable (MY_TARGET_HOST).

Taurus jMeter Example 3

Running JMeter test

Two folders will created on each test run. “report” (configured in YAML) and “Artifacts” (as Date/Time string). Attention – report.xml will replaced on each run!

Jenkins and Virtualenv

This guide is intended to show how you can use Jenkins/Hudson with Python virtualenv.




Create (if necessary) a new “Freestyle Project” and configure as needed build-paramaters , VCS and etc. On section “Build” – “Execute Shell” insert following script.

Jenkins – Modern Status Plugin

Who the original symbols of Jenkins do not like, should try the Modern Status Plugin. The tiny plugin of Oliver Vinn provide a new and very cool set of icons for the continuous integration server. The installation is very simple!


This is a example of original icons:

jenkins original status icons

Open the Plugin Manager and search for “Modern Status Plugin”.

jenkins modern status plugin

After restart Jenkins the new iconset should be available and look like:

jenkins modern status

Sass, Compass and Jenkins

This tutorial shows how Sass, Compass and Jenkins working together in very easy way. The goal is that Jenkins created the CSS from SCSS files.


  • Jenkins installed
  • Ruby installed


In first step we need to install Sass and Compass on the clients (Developer engines) and build server (Jenkins).

Now we create on one client the project.

Now add and edit some content to the files with your favorite editor and commit all to your repository. The content for the tutorial looks like this:

Okay… now lets go to Jenkins. Here we create a new “Freestyle Job” and configure the Source-Code-Management and insert the following command into “Execute Shell”

Thats it… after running the build into the workspace you should see the folder “css” and a file “style.css” the content should look like:


Publish continuous integration status on Desktop

In one of my last tutorials, i show how to develop test tools for software tester with Python. Now i will show you, how to publish continuous integration status information for other team members like Scrum master, Product owner or Test manager.



If you don`t have Jenkins or Hudson running, search some public services with Google!

Example: inurl:8080 intitle:”Dashboard [Jenkins]”


Create a python script like this:

Now start GeekTool and create a new Geeklet. Drag a Shell Geeklet on you Desktop. Now insert values for name, size, set colors and so on and add the python script on “Command”.

Create Geeklet

… the script.

Geeklet Command

Thats it! Now you can export the Geeklet and share it with you team members. My current screen looks like:

Geeklet result

Jenkins and jslint4java

This tutorial shows a very simple Jenkins – jslint4java integration over Shell.


  • Jenkins is installed


Start Jenkins, open the browser (http://<host>:8080) and setup a new “Free Style Project” (JS-Lint-Example).

Jenkins Freestyle Project
The tutorial does not use any VCS, so we press the “Build Now” button to create the project “workspace” folder. After successful creation, we create 3 new folders (src, lib, build) inside the workspace folder.

Now upload the jslint4java into the “lib” folder.

It`s time to test if jslint4java is running. The 1st test in terminal self.

The 2nd test direct on Jenkins. Open the “JS-Lint-Example” job in browser – press link “Configure” and we create a “Build-Step” with “Execute Shell”.

Jenkins JSLint Test

After save and build the “Console Output” of the respective build should show the help. If there is a problem here, please check if Java is installed and the file permissions are correct. If everything works fine we create a simple JavaScript file and upload this into the “src” folder.

Now we change the “Execute Shell” command and add the “Post-Build-Action” – “Publish JUnit Test Results” with value “build/js_report.xml”.

Jslint Jenkins Configuration

Ready,… after save and new build we can see the file “js_report.xml” into “build” folder and the jUnit  report into our project.

Jslint Jenkins jUnit Report

Embed SLOCCount into Jenkins jobs


Install SLOCCount and cloc on system.


Search and install the “SLOCCount Plugin”.

jenkins sloccount plugin


Now search your job and start configuration and insert the command “Build > Execute Shell”.

As last step add the Post-Build-Action – “View SLOCCount results” and insert the generated report “”.

sloccount result path

The plugin just show the number of lines per file, file type and folder. No estimated project value or other informations! This information you can see direct on generated report.

After running the build, your screen should look similar like this:

sloccount report