← Back to team overview

kicad-developers team mailing list archive

[PATCH 0/1] Experimental code for running tests separately



this is not meant for immediate merging, but maybe of interest to some:
this patch splits the test cases inside the Boost.Test based tests in a way
that is visible to CTest.

The downside is that running the tests now takes ages because Boost.Test
setup is really slow, the upside is that individual test cases show up in
the log, and no trickery with logfiles is needed. Running valgrind on
individual tests is also possible in theory, but useless in practice
because glib doesn't have an equivalent to __libc_freeres(), so we get 294
false positives from glib for every test.

If someone wants to pursue this further, here is the code.


Simon Richter (1):
  Split Boost.Test based tests

 CMakeModules/BoostTest.cmake         | 204 +++++++++++++++++++++++++++
 CMakeModules/BoostTestAddTests.cmake | 138 ++++++++++++++++++
 qa/CMakeLists.txt                    |   1 +
 qa/common/CMakeLists.txt             |   6 +-
 qa/eeschema/CMakeLists.txt           |   2 +-
 qa/libs/sexpr/CMakeLists.txt         |   2 +-
 qa/pcbnew/CMakeLists.txt             |   2 +-
 qa/utils/kicad2step/CMakeLists.txt   |   2 +-
 8 files changed, 350 insertions(+), 7 deletions(-)
 create mode 100644 CMakeModules/BoostTest.cmake
 create mode 100644 CMakeModules/BoostTestAddTests.cmake


Follow ups