Changes between Version 2 and Version 3 of FATE/TestingCoverage


Ignore:
Timestamp:
Mar 20, 2014, 5:58:30 AM (5 years ago)
Author:
Timothy_Gu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FATE/TestingCoverage

    v2 v3  
    22
    33One 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].
     4
     5== Prerequisites ==
     6
     7You 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).
     8
     9On Debian-derived systems, you can just do:
     10
     11{{{
     12sudo apt-get install gcov lcov
     13}}}
     14
     15If you want to use `gcovr` instead, you can do:
     16
     17{{{
     18sudo apt-get install gcov python-setuptools
     19sudo easy_install gcovr
     20}}}
     21
     22{{{
     23#!div style="border: 1pt dotted; margin: 1em; background-color: #fffff9;"
     24'''Note''': The `gcovr` package in Ubuntu Saucy or earlier is too old to generate HTML output.
     25}}}
    426
    527== `./configure` ==
     
    3658== Using gcovr ==
    3759
    38 '''WIP'''
     60Run the FATE suite:
     61
     62{{{
     63# The -j parameter controls thread number for parallel building
     64make -k -j6 fate
     65}}}
     66
     67Then generate output:
     68
     69{{{
     70gcovr -b -r $SOURCEDIR -e '/usr/.*' --html --object-directory $OBJDIR
     71}}}