| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michelle Caisse <Michelle(dot)Caisse(at)Sun(dot)COM> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Generating code coverage reports |
| Date: | 2008-07-10 20:19:52 |
| Message-ID: | 13595.1215721192@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-07-10 20:27:31 | Re: gsoc, text search selectivity and dllist enhancments |
| Previous Message | Jan Urbański | 2008-07-10 20:15:04 | Re: gsoc, text search selectivity and dllist enhancments |