Hi,
On Wed, Jun 03, 2015 at 02:33:23PM +0100, Michael Meeks wrote:
It is noticeable that where there are existing tests & infrastructure,
new tests are easier to create and often there are more of them - so are
there places where we should work to create infrastructure ?
Is there something we can improve by throwing hardware at it ? as we
have done for the crash-testing; if so what hardware is needed ?
So, with the experience of creating a lcov dump last week, another that would
be helpful would be a box creating lcov reports, say once a week, with the same
configuration if possible to really allow comparing them over time and identify
trends. Having good longterm trends for this would also be valuable, just as
having something to show for test coverage improvements and to credit those
that do this work.
Best,
Bjoern
Context
- why a master-tested branch is important and incentives for CI over no-CI (was: test infrastructure ideas appreciated ...) (continued)
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.