Changes between Version 2 and Version 3 of FATE/TestingCoverage

Timestamp:

Mar 20, 2014, 3:58:30 AM (12 years ago)

Author:

Timothy Gu

Comment:

--

FATE/TestingCoverage

@@ -2 +2 @@
 
 One can easily discover untested components of FFmpeg using coverage testing. A online coverage report is available at [http://coverage.ffmpeg.org/], but you can generate one yourself with [http://gcc.gnu.org/onlinedocs/gcc/Gcov.html gcov] and either [http://ltp.sourceforge.net/coverage/lcov.php lcov] or [http://gcovr.com/ gcovr].
+
+== Prerequisites ==
+
+You have to use `gcov` for generating coverage information. If you want a good-looking HTML layout of the coverage information, you will need either `lcov` or `gcovr` (3.0 or later).
+
+On Debian-derived systems, you can just do:
+
+{{{
+sudo apt-get install gcov lcov
+}}}
+
+If you want to use `gcovr` instead, you can do:
+
+{{{
+sudo apt-get install gcov python-setuptools
+sudo easy_install gcovr
+}}}
+
+{{{
+#!div style="border: 1pt dotted; margin: 1em; background-color: #fffff9;"
+'''Note''': The `gcovr` package in Ubuntu Saucy or earlier is too old to generate HTML output.
+}}}
 
 == `./configure` ==
@@ -36 +58 @@
 == Using gcovr ==
 
-'''WIP'''
+Run the FATE suite:
+
+{{{
+# The -j parameter controls thread number for parallel building
+make -k -j6 fate
+}}}
+
+Then generate output:
+
+{{{
+gcovr -b -r $SOURCEDIR -e '/usr/.*' --html --object-directory $OBJDIR
+}}}