Re: convert libpq uri-regress tests to tap test - Mailing list pgsql-hackers

From Tom Lane
Subject Re: convert libpq uri-regress tests to tap test
Date
Msg-id 1276236.1645667561@sss.pgh.pa.us
Whole thread Raw
In response to Re: convert libpq uri-regress tests to tap test  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: convert libpq uri-regress tests to tap test  (Andrew Dunstan <andrew@dunslane.net>)
Re: convert libpq uri-regress tests to tap test  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
> On 23.02.22 23:58, Tom Lane wrote:
>> Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
>>> libpq TAP tests should be in src/interfaces/libpq/t/.

>> That's failing to account for the fact that a libpq test can't
>> really be a pure-perl TAP test; you need some C code to drive the
>> library.

> Such things could be put under src/interfaces/libpq/test, or some other 
> subdirectory.  We already have src/interfaces/ecpg/test.

OK, but then the TAP scripts are under src/interfaces/libpq/test/t,
which isn't what you said.  I have no great objection to moving
src/test/modules/libpq_pipeline/ to src/interfaces/libpq/test/,
though, as long as the buildfarm will cope.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Design of pg_stat_subscription_workers vs pgstats
Next
From: Masahiko Sawada
Date:
Subject: Re: Failed transaction statistics to measure the logical replication progress