Change Details

The dynamic analysis reports that are or could get reported to CDash are currently not very useful. Suggested improvements: - evaluate sanitizers instead of or as an addition to valgrind: https://blog.kitware.com/ctest-cdash-add-support-for-new-dynamic-analysis-tools/ - create MITK-specific CMake variables to enable analysis on a per-module basis to start with a small set of tests - evaluate reporting on the newer CDash version which we will implement soon This task is meant to track overall progress and discussions. Bigger code changes should go to sub-tasks

The dynamic analysis reports that are or could get reported to CDash are currently not very useful. Suggested improvements: - evaluate sanitizers instead of or as an addition to valgrind: https://blog.kitware.com/ctest-cdash-add-support-for-new-dynamic-analysis-tools/ - create MITK-specific CMake variables to enable analysis on a per-module basis to start with a small set of tests - also define coverage goals on a per-module basis as well using CMake variables - evaluate reporting on the newer CDash version which we will implement soon, this should make it easy e.g. to spot Core classes without a unit test, which has previously be done manually (e.g. T13692 T13690) This task is meant to track overall progress and discussions. Bigger code changes should go to sub-tasks. .

The dynamic analysis reports that are or could get reported to CDash are currently not very useful. Suggested improvements: - evaluate sanitizers instead of or as an addition to valgrind: https://blog.kitware.com/ctest-cdash-add-support-for-new-dynamic-analysis-tools/ - create MITK-specific CMake variables to enable analysis on a per-module basis to start with a small set of tests - evaluate reporting on the newer CDash version which we will implement soon This task is meant to track overall progress and discussions. Bigger code changes should go to sub-taskalso define coverage goals on a per-module basis as well using CMake variables - evaluate reporting on the newer CDash version which we will implement soon, this should make it easy e.g. to spot Core classes without a unit test, which has previously be done manually (e.g. T13692 T13690) This task is meant to track overall progress and discussions. Bigger code changes should go to sub-tasks. .