The gcov plugin should have better control over what gets coverage analysis

[austinglaser]

Currently, the gcov plugin may falsely assume some files need coverage that don't. For instance, a helper module containing reusable stubs for use as CMock callbacks will currently get coverage analysis.

We could try to get smarter with the logic determining which files should get coverage, but I suspect that this could be a rabbit hole, and is prone to frustrating problems.

I propose that instead we add a couple of parameters to the config:

• :exclude: A lilst of files to explicitly exclude from coverage analysis
• :include: A list of files to explicitly include in coverage analysis. We only really need this if we plan to include smarter logic which might sometimes get things wrong

[tobyjwebb]

Hi!

I'd like to implement the :exclude logic, unless anyone is already working on this? (I may need include logic also, but the exclude is more urgent for the time being.)

@mvandervoord

NOTE: I was having this problem because I was getting the local Ceedling/vendor headers in the html report. I've created a pull request that ignores this directory.

I believe you can also configure what gets excluded by configuring the :html_report_filter: regex (under :gcov: in the project.yml file).

[mvandervoord]

@tobyjwebb -- yes please! If you get something this week, I can even roll it into the upcoming release!