On 17 October 2017 at 15:02, Dan Rue dan.rue@linaro.org wrote:
What I would like to see, and I don't know if it is even possible, is something that actually measures test coverage based on code paths in the linux kernel so that we have a means to actually measure our effectiveness. If we knew we were testing 43% (number pulled out of thin air) of the linux kernel code paths, then we would know what areas to focus on to bring that number up, and we would know which subsystems to have some confidence in, and which are uncovered.
Naresh did gcov with kernel some time ago, but that wasn't trivial IIRC. It requires to have the sources and symbols to be present in the root filesystem. It also requires some build time instrumentation so it's not transparent.
milosz