Re: Generating code coverage reports

It should be possible to make it work for a VPATH build with
appropriate arguments to gcov and lcov, but currently it expects the
object files and generated data files to be in the build directory.

You need access to the build tree to generate coverage statistics and to
generate the report with "make coverage" after running the tests or
application.

-- Michelle

Tom Lane wrote:

>Michelle Caisse <Michelle(dot)Caisse(at)Sun(dot)COM> writes:
>
>
>>I have a patch that I will be submitting to add to the build system the
>>capability of reporting on test code coverage metrics for the test
>>suite.
>>
>>
>
>Cool.
>
>
>
>>To generate coverage statistics, you run configure with
>>--enable-coverage and after building and running tests, you do make
>>coverage. The process generates data files in the same directories as
>>source & object files and produces a coverage directory at the top level
>>with the html files.
>>
>>
>
>How does that work with a VPATH build? Are you trying to say that you
>still have to have the original build tree around in order to collect
>coverage data?
>
> regards, tom lane
>
>
>

--
Michelle Caisse Sun Microsystems
California, U.S. http://sun.com/postgresql