Unfortunately I cannot see any colored lines in the CDash html but it's ok since I'm able to see the output in the provided link.
@nolden can you shed any light on this?

If I look at the outputs side by side there is e.g. a difference in the SetSecondaryMask method: it's called 24 times in the CDash run but in the OpenCppCoverage it's red. Which tests did you execute? I think if I remember correctly the numbers in the CTest/CDash result are aggregated over all tests in the default config. Could this make the difference?

I executed all tests in files.cmake, which are: mitkImageStatisticsCalculatorTest, mitkPointSetStatisticsCalculatorTest, mitkPointSetDifferenceStatisticsCalculatorTest, mitkImageStatisticsTextureAnalysisTest, mitkImageStatisticsContainerManagerTest and mitkImageStatisticsHotspotTest.
But I think the reason for the different results might be that opencppcoverage does not use any testfiles and cannot load pictures because it cannot find these and there is no option to pass them to opencppcoverage.

In T27289#197693, @nolden wrote:

If I look at the outputs side by side there is e.g. a difference in the SetSecondaryMask method: it's called 24 times in the CDash run but in the OpenCppCoverage it's red. [...]

That's exactly what we werelooking at. Difference in percentage is because of the different number of lines / functions not hit by the tests. The question was, why are the functions not reached by OpenCppCoverage.

In T27289#197725, @j762e wrote:

But I think the reason for the different results might be that opencppcoverage does not use any testfiles and cannot load pictures because it cannot find these and there is no option to pass them to opencppcoverage.

Ok, I think this is the reason for the difference and I think this has to be fixed to make the output of OpenCppCoverage meaningful. Many tests just don't do anything useful without test images. You can find the proper command line to start the test if you execute "ctest -V -R <test-name>" in the MITK-build directory, or look it up on CDash and adapt the paths to your local setup. E.g. look here and click "Show command line":

http://cdash.mitk.org/testDetails.php?test=13770846&build=724301