On Thu, May 21, 2015 at 10:19 AM, Brad King <[email protected]> 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
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
