[cmake-developers] Running coverage tool with environment (was: CMake strips MAKEFLAGS from environment)

[Taylor Braun-Jones]

On Thu, May 21, 2015 at 10:19 AM, Brad King <brad.king at kitware.com> wrote:

> We typically run coverage as part of nightly testing with a 'ctest -S'
> dashboard client script.  The script surrounds the actual build
> invocation and can take responsibility for adding things like COVFILE
> to the environment.
>

Ya, that was one of my first thoughts and it does make things simpler. But
I wanted developers to be able to get instant coverage feedback at their
desktop to shorten the write test/check coverage cycle. We have high MC/DC
coverage goals and as you start to approach 100% coverage it's not always
obvious what conditions/decisions are the missing coverage. I also want to
keep the usage simple and consistent meaning that code coverage and static
analysis reports should be available as a build target (e.g. `make
coverage_report coverity_report`)

Taylor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20150521/2dd0014a/attachment-0001.html>