Re: Rewriting the test of pg_upgrade as a TAP test - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Rewriting the test of pg_upgrade as a TAP test
Date
Msg-id CAOuzzgoTyw+tW063W4A_UAj9SAqtHBTqgU_cE-4eGSS7V7kK_g@mail.gmail.com
Whole thread Raw
In response to Re: Rewriting the test of pg_upgrade as a TAP test  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Rewriting the test of pg_upgrade as a TAP test
List pgsql-hackers
Michael,

On Mon, Apr 3, 2017 at 18:29 Michael Paquier <michael.paquier@gmail.com> wrote:
On Tue, Apr 4, 2017 at 12:12 AM, Stephen Frost <sfrost@snowman.net> wrote:
> I'm very curious what you're thinking here?  IIRC, Andrew had some ideas
> for how to do true cross-version testing with TAP in the buildfarm, but
> I don't think we actually have that yet..?

I heard about nothing in this area. Cross-branch tests may be an
interesting challenge as tests written in branch X may not be in Y.
The patch presented here does lower the coverage we have now.

Not good if it lowers the coverage, but hopefully that's fixable. Have you analyzed where we're reducing coverage..?


Of course, it's possible I misunderstood..

That seems focused on upgrading and I'd really like to see a general way to do this with the TAP structure, specifically so we can test pg_dump and psql against older versions.  Having the ability to then be run under the coverage testing would be fantastic and would help a great deal with the coverage report. 

Thanks!

Stephen

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Candidate for local inline function?
Next
From: "David G. Johnston"
Date:
Subject: Re: Variable substitution in psql backtick expansion