On Tue, 2010-01-12 at 03:38 -0500, Behdad Esfahbod wrote: > On 01/04/2010 12:53 PM, Javier Jardón wrote: > > Hello, > > > > The objective of the GnomeGoal is to add code coverage of your code > > with GCOV [1] > > You can take a look to the GnomeGoal page here: [2] (There are also > > examples to add GCOV support to json-glib and libgdata) > > I was a huge fan of adding GCOV support to all modules, and actually have > patches for glib/pango/gtk+ in bugzilla. But after finding out that coverage > can be extracted without modifying the modules (like build.gnome.org is > already doing), I'm against cluttering the modules with GCOV boilerplate. Having the gcov stuff in-tree means that you can test the coverage of new code as you write it, so you could theoretically always have 100% coverage of the code which is committed. Similarly, build.gnome.org only tests the versions of modules in the current jhbuild moduleset, not the latest git versions. It's not much boilerplate code anyway, so I thought it was useful for libgdata. To each their own. :-) Philip > behdad > > > > As a side effect, the idea is encourage devels to: > > - Use the new Glib and GTK+ test frameworks [3] and [4] > > - Use build.gnome.org service. For example, take a look to Glib coverage [5] > > > > All the info is available in the GnomeGoal/AddCodeCoverage page. > > > > Comments / suggestions welcomed. > > > > [1] http://gcc.gnu.org/onlinedocs/gcc/Gcov.html > > [2] http://live.gnome.org/GnomeGoals/AddCodeCoverage > > [3] http://library.gnome.org/devel/glib/stable/glib-Testing.html > > [4] http://library.gnome.org/devel/gtk/stable/gtk-Testing.html > > [5] http://fixed.gnome.org/coverage/glib/lcov/ > _______________________________________________ > desktop-devel-list mailing list > desktop-devel-list gnome org > http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Attachment:
signature.asc
Description: This is a digitally signed message part