Here, I’m trying to use travis-ci, c++, github, CATCH, premake together with my undoredo-cpp library to reduce entropy, try out continuous integration and behavior-style tests.
As a “one-man show” programmer at least at home, I’m trying to keep the discipline of writing tests first. “Growing Object-Oriented Software Guided by Tests” is perhaps a good, although a comparatively dry book for those who are not yet convinced. The blog post by Phil Nash about his latest version of the c++ single-header testing framework CATCH, moved me to finally get my hands on the free continuous integration service travis-ci, along with CATCH with a goal to rewrite the tests for my undo-redo c++ adventure in a more behavior-driven-style.
The undo-redo library is already there, and the tests as well – in gtest (see the master branch). I’d label them “explorative” at the moment since there are just too many assertions per test case, which means I’m repeating myself.
Starting continuous integration at travis-ci for c++
To start my CATCH-“BDD” exploration I’ve setup the branch first: https://github.com/d-led/undoredo-cpp/tree/catchmoci. At my landing page the project is switched on for catching the commit hooks:
The following configuration file
.travis.yml is placed for travis-ci to know what to do with my non-conforming repo:
language: cpp branches: only: - catchmoci before_script: ls script: - make -C Build
As in all TDD practice, the build fails due to the reason that the build doesn’t work yet at all. Adding a status image to my README shines:
Fixing the build
The makefiles are created using premake4, which is a single-file makefile generator based on lua. Unfortunately, I couldn’t force the CI-virtual machine execute my binary premake4, so I had to add the generated makefiles. Now that the make process works, the tests still don’t compile:
Fixing the tests
Once the bulk of the assertions have been rewritten for CATCH, the build still failed due to an ambiguity in serializing
std::nullptr_t. Fortunately, Phil has thought of (or rather tested) that, and has a macro which can be defined for the build, fixing it:
Voila, travis-ci vm is happy:
Just checking locally if test reporting is fine by adding a spurious test temporarily:
The test-rewrite has been successful and all pass, the badge is green and I can go to bed
But! It’s not the end of the story! BDD! Mock-objects!