Re: Re: Email to hackers for test coverage

From: "movead(dot)li(at)highgo(dot)ca" <movead(dot)li(at)highgo(dot)ca>
To: "Peter Eisentraut" <peter(dot)eisentraut(at)2ndquadrant(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Re: Email to hackers for test coverage
Date: 2019-08-29 01:14:49
Message-ID: 2019082909144716972158@highgo.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2019-08-29 00:43, peter(dot)eisentraut(at)2ndquadrant(dot)com wrote:


> Make spaces and capitalization match surrounding code.
>That's fine, but I suggest that if you really want to make an impact in
>test coverage, look to increase function coverage rather than line
>coverage. Or look for files that are not covered at all.

Thanks for pointing all the things, I will reconsider my way on
code coverage work.

--
Movead

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-08-29 01:44:58 Re: Improve error detections in TAP tests by spreading safe_psql
Previous Message Thomas Munro 2019-08-29 01:06:32 Re: gharial segfaulting on REL_12_STABLE only