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

From Andrew Dunstan
Subject Re: convert libpq uri-regress tests to tap test
Date
Msg-id 95fdebab-adaa-4d00-165b-e58b9b63b94d@dunslane.net
Whole thread Raw
In response to Re: convert libpq uri-regress tests to tap test  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: convert libpq uri-regress tests to tap test  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On 2/23/22 20:52, Tom Lane wrote:
> 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.
>
>             


It won't without some adjustment.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Add id's to various elements in protocol.sgml
Next
From: Peter Eisentraut
Date:
Subject: Re: Design of pg_stat_subscription_workers vs pgstats