add coverage analysis to unit tests
Background: Feedback loop in testing is missing, we need to add that. Example is here:
Skills: shell scripting, Makefile reading
Link given in previous comment is 404-AWOL at the moment. Should it perhaps be <http://redmine.digitalstrom.org/projects/dss/wiki/Generate_coverage_report>?
Deteted "Easyhack" from summary
bfo mentionned Thunderbird coverage there http://people.mozilla.org/~jcranmer2/c-ccov/ (quote from http://nabble.documentfoundation.org/LibreOffice-code-coverage-tp3994901.html).
lcov is a front to gcov (see http://gcc.gnu.org/onlinedocs/gcc/Gcov.html). Leafing through the url, it seems quite straightforward to generate the data coverage file. Of course, there's after all the instrumentalization around this for a project of a size of LO. Perhaps a specific "Tinderbox" could help ?
Another example - Firefox coverage:
Seems there is a trace of gcov work in the source already:
Added the URL that contains the lcov report(s).
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility.
see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
17:25 < Sweetshark_> sberg, erAck_away: can fdo#38840 be closed?
17:33 <@sberg> Sweetshark_, how do I know? /you/ filed that issue ;) and yes, we have the machinery now, even though we do not make any
use of it (yet?), so the bug can probably be closed indeed
=> thus closing, best file a new EasyHack with the exciting new things to build on top of this when needed.
Migrating Whiteboard tags to Keywords: (EasyHack DifficultyBeginner SkillScript )
Remove LibreOffice Dev List from CC on EasyHacks
(curtailing excessive email to list)