Project

General

Profile

Actions

Unit Tests

The idea behind unit tests is "does this function do what I think it's doing". We want to check that, when we write a function, we haven't put any subtle (or not so subtle) errors in the code. Also we want to check that when we change some other function, it doesn't break existing code. So for each function (or maybe pair of functions) we write a test function. These are known as "unit tests".

Unit testing is an essential part of the QA process for MAUS, so that

Code which is not unit tested is not eligible for release in MAUS. This includes, for example, all code in the ${MAUS_ROOT_DIR}/src directory.

Also note that tests are code that we need to edit, etc, so tests should obey any relevant style guides.

In general:
  • Code which is in common_cpp should have tests in cpp_unit; tests are written in the gtest framework
  • Code which is in common_py should have tests in py_unit; tests are written in the unittest framework
  • Code which is in input, map, reduce areas should have tests in the relevant input, map, reduce subdirectories; typically we use the SWIG interface and write tests in python even for C++ code

C++ unit tests

In C++ we use the google testing framework which has some convenience functions for e.g. equality testing in the presence of floating point errors, setting up common test data, etc. The google test framework should have been installed during the third party libraries. The C++ tests are found at

${MAUS_ROOT_DIR}/tests/cpp_unit
Sconstruct builds a unit test application in build/test_cpp_unit that you can just run from the command line.

Go ahead and edit the tests if you need to. We should have one source file for each header file in the main body of the code. Each directory in ${MAUS_ROOT_DIR}/src/common/* should be a directory in ${MAUS_ROOT_DIR}/tests/cpp_unit. If you want to add an extra test, you need to make sure that it includes gtest

#include "gtest/gtest.h"
It should be automatically added to the test executable by scons.

To run the tests, either run the full python unit testing suite, or run just the cpp tests by running executable build/test_cpp_unit (after building). If you are just interested in a specific test, you can do e.g.

build/test_cpp_unit --gtest_filter=VirtualPlaneTest.* --verbose_level=0
to run all tests from VirtualPlaneTest with verbose_level set to debug

Google tests documentation

Python unit tests

In Python we use the internal unittest module for a unit testing framework. Python unit tests are found at

${MAUS_ROOT_DIR}/tests/py_unit
Feel free to edit or add extra unit tests if you need to. We should have one python source file for each python source file in the main body of the code.

unittest documentation

Module Tests

Module tests are found in the same directory as the relevant modules - so a module is something in input, map, reduce, output. Module tests also use the unittest framework and are written in python.

More on the unit test concept

The idea behind unit tests is to test at the level of the smallest unit that the code does what we think. We test at the smallest unit so that:

  • test coverage is high
  • tests are quick to run
  • we get logically separated functions

Let's consider each of these points individually

  • test coverage is high - if we imagine the execution path following some branch structure, then we get many more possible execution paths for longer code snippets. So maintaining high test coverage becomes very difficult, and we need many more tests to have good test coverage.
  • tests are quick to run - the execution time goes as the (number_of_tests)*(length_of_each_test). Now, we have many more tests to keep a good test coverage, and each test is longer because they are testing bigger code snippets. This means tests are slowwww. You want to actually run the tests, and an essential part of this is making sure they are quick enough.
  • we get logically separated functions - functions that do simple, understandable things are less likely to be buggy than functions that do complicated or difficult things. The process of really testing if a function does what you intended forces us to make code simple and understandable - otherwise the test becomes difficult to write.

Explicitly, unit tests are not intended to test: that code works together in the desired fashion, code integrates properly with external libraries, the load on hardware is not too big, etc. These issues are dealt with in the Application tests.

Updated by Rogers, Chris about 8 years ago ยท 18 revisions