| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RFC: adding pytest as a supported test framework |
| Date: | 2024-06-12 17:30:33 |
| Message-ID: | FAC2FCFE-8C70-4996-9598-34DD7596BB41@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 12 Jun 2024, at 17:50, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2024-06-11 07:28:23 -0700, Jacob Champion wrote:
>> The OAuth pytest suite makes extensive use of
>> - psycopg, to easily drive libpq;
>
> That's probably not going to fly. It introduces painful circular dependencies
> between building postgres (for libpq), building psycopg (requiring libpq) and
> testing postgres (requiring psycopg).
I might be missing something obvious, but if we use a third-party libpq driver
in the testsuite doesn't that imply that a patch adding net new functionality
to libpq also need to add it to the driver in order to write the tests? I'm
thinking about the SCRAM situation a few years back when drivers weren't up to
date.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniele Varrazzo | 2024-06-12 17:38:54 | Re: RFC: adding pytest as a supported test framework |
| Previous Message | Ranier Vilela | 2024-06-12 17:18:57 | Re: Columnar format export in Postgres |