Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


Hi Maarten,

On Mon, Nov 03, 2014 at 09:58:25AM +0100, Maarten Hoes <hoes.maarten@gmail.com> wrote:
I was just trying to follow this LCOV Code Coverage guide:

https://wiki.documentfoundation.org/Development/Lcov

which recommends to run configure '--with-system-libs' in order to easily
filter 'non-core' / non-libreoffice code from the resulting lcov report.
Perhaps this needs a different approach, then.

Is there a specific area in which you're interested wrt. code coverage?

There is
<http://cgit.freedesktop.org/libreoffice/contrib/dev-tools/tree/lcov/coverage.sh>
that is a start of mapping source code locations to unit tests, that can
give you much quicker feedback if you plan to do "pick an untested area,
writer a unit test, re-check if the test indeed increased coverage"
cycles.

Regards,

Miklos

Attachment: signature.asc
Description: Digital signature


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.