Automatic testing with Robot Framework pt. III: Setting up a continuous integration system

Third time’s the charm. In my two previous video posts (part 1 & part 2) I taught you to write automatic, maintainable tests for your web application. To leave out unnecessary manual work, the tests should also be executed automatically by a continuous integration system. This is usually done after changes have been made in the code, the system, or according to a predefined schedule.

This time I’ll show how to install and configure an open-source continuous integration server tool for running our Robot Framework + Selenium tests. I use Jenkins at its simplest, and set up the CI system from scratch. The tests are fetched from a Git repository that is hosted in Deveo, and they are executed in parallel with three different browsers. I implement this by setting up a multi-configuration project that executes three shells in one environment. Jenkins’ Robot Framework plugin is also used for visualizing the test results in a neat way. Twelve minutes of video in total, and we’ve implemented and refactored browser tests that use Robot Framework and its Selenium2Library, executed the tests many times, and even set up a continuous integration system to run the test set in parallel with different browsers, and to publish the results on a web page. It wasn’t hard at all, was it?

Previous posts in the series