Changes between Version 1 and Version 2 of FATE/TestingCoverage

Timestamp:

Mar 20, 2014, 3:43:47 AM (12 years ago)

Author:

Timothy Gu

Comment:

--

FATE/TestingCoverage

@@ -3 +3 @@
 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].
 
-== Getting Started ==
+== `./configure` ==
 
-'''WIP'''
+First, configure the build with the special gcov toolchain:
+
+{{{
+./configure --toolchain=gcov --rest-of-options
+# For example, I use:
+# ./configure --toolchain=gcov --enable-gpl --enable-avresample --samples=`pwd`/fate-suite
+}}}
 
 == Using lcov ==
 
-'''WIP'''
+If you are using lcov, you have to first reset its counter:
+
+{{{
+make lcov-reset
+}}}
+
+Then, run the FATE suite:
+
+{{{
+# The -j parameter controls thread number for parallel building
+make -k -j6 fate
+}}}
+
+Finally, generate the HTML output:
+
+{{{
+make lcov
+}}}
 
 == Using gcovr ==