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
expectsthe object files and generated data files to be in the build directory.<br /><br /> You need access to the build
treeto generate coverage statistics and to generate the report with "make coverage" after running the tests or
application.<br /><br /> -- Michelle<br /><br /> Tom Lane wrote: <blockquote cite="mid13595.1215721192@sss.pgh.pa.us"
type="cite"><prewrap="">Michelle Caisse <a class="moz-txt-link-rfc2396E"
href="mailto:Michelle.Caisse@Sun.COM"><Michelle.Caisse@Sun.COM></a>writes: </pre><blockquote type="cite"><pre
wrap="">Ihave 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.   </pre></blockquote><pre wrap="">
Cool.
 </pre><blockquote type="cite"><pre wrap="">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.   </pre></blockquote><pre wrap="">
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
 </pre></blockquote><br /><pre class="moz-signature" cols="72">-- 
Michelle Caisse               Sun Microsystems
California, U.S.     <a class="moz-txt-link-freetext" href="http://sun.com/postgresql">http://sun.com/postgresql</a>

</pre>