[ITK] A suggestion to manage code coverage drops

[Jon Haitz Legarreta]

Hi,
I'm wondering whether with the current code coverage tools/CI used, and
without excessive work and burden, we would be able to spot merge requests
or commits that lower the code coverage.

That is, automatically performing a kind of diff between two code coverage
reports and identifying the commits (and, thus, the files) that actually
make the coverage figure change. Or at least, those that make the figure
decrease.

If I'm not mistaken some CI tools already provide a coverage report (or at
least the figure) for each commit (not 100% sure). I guess that would
ideally allow maintainers to take action before a topic or commit makes its
way into master.

For example, that would allow to automatically ask the developer to raise
the coverage, or setting some policy to require at least say, a 95%
coverage in new files, or to keep the coverage figure when modifying
existing files, although this last may be unfeasible in practice.

I am well aware that even if this were possible, it would require some
investigation. I am ready to help.

Thanks,
JON HAITZ

--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/community/attachments/20170117/13f59795/attachment.html>