On Wed, Dec 10, 2014 at 5:27 AM, Maarten Hoes <hoes.maarten@gmail.com> wrote:
However, doesnt the 'make it run it all in one call' implementation conflict
at least a little with the previously stated desire to run the code coverage
on other tests than just 'make check' ?
again being flexible does not mean that one could not propose sensible
'default'.
Its the main reason I split
everything up in -before' and '-after' parts, so that you can easily run any
test you desire in between.
yeah that is a great feature... I have not removed it in anyway. just
expended things a bit to implify my use case.
Norbert
Context
- Re: Scheduling lcov code coverage script (continued)
Re: Scheduling lcov code coverage script · Norbert Thiebaud
Re: Scheduling lcov code coverage script · Maarten Hoes
Re: Scheduling lcov code coverage script · Norbert Thiebaud
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.