The idea behind unit tests is to check "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 development process for OPAL. Also note that tests are code that we need to edit, etc, so tests should obey any relevant style guides.
tests/tools/install_gtests.bashto install gtest framework (does not work on macs)
From the root opal source directory run
tests/opal_unit_teststo run the unit tests
Setting up the tests
In OPAL 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.
There is a script for installing gtest in
At the moment it doesn’t work on macs - sorry about that.
Documentation for gtest can be found at:
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.
The directory structure is supposed to reflect the directory structure of the main OPAL source (add a directory if you need to).
If you want to add an extra test, you need to make sure that it includes gtest
It should be automatically added to the test executable by cmake.
To run the tests, either run the full regression testing suite,
or run just the cpp tests by running executable test/opal_unit_tests (after building).
If you are just interested in a specific test,
you can do e.g.
tests/opal_unit_tests --gtest_filter=SBend3DTest.* to run all tests from SBend3DTest.
There are some other useful command line options; do
tests/opal_unit_tests --help to list them all.
Unit tests are in the directory
Code which is in src/Classic should have tests in
Other code should have tests in
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. Thus its a good idea to test the smallest code snippet possible.
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 Regression tests.
Test driven design (TDD)
Test driven design (TDD) is a recommended way to design code in which unit tests come for free.
Instead of class design, TDD starts by writing the unit tests. This focuses directly on the usage of the new classes / features.
By putting the test first and then writing code to make the test pass, TDD becomes a way to design code. Even better, as you add tests you incrementally improve your design. In an environment that (deliberately) lacks detailed, up-front design thinking, that last characteristic is critical. The process works so well, in fact, that the architecture that emerges from a TDD environment is usually better than the one that, I at least, can create from whole cloth ahead of time.
TDD consists of the following steps:
Write unit tests
Unit test does not compile
Write class/feature design (skeleton)
Unit test will compile, but fail
Write class/feature implementation
Unit test will pass (if implementation correct)