Unit tests

We ensure the basic level of integrity by automatically building all repositories several times a day and running unit-tests. This can eliminate the following errors:

• General compilation errors caused by syntax errors, missing includes, wrong include paths.
• Missing files that are available locally but not checked into the repo.
• Hardcoded local paths for files required for build-tests.
• Depending on the unit-test coverage, this checks the correct functioning of the software.

Gtest

We use gtest (install from Ubuntu packages) for unit tests. In catkin and catkin simple, google-tests can be simply added as follows:

catkin_add_gtest(test_xyz test/xyz-test.cc)
target_link_libraries(test_xyz gtest)

Naming convention

Eigen checks