| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RFC: adding pytest as a supported test framework |
| Date: | 2024-06-12 19:34:04 |
| Message-ID: | CAOYmi+nE2mJwZ6ZL-FuQPk6iJB+tHMG+wjdy6egvxPRcfoX3OA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 12, 2024 at 10:30 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> 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 use the third-party driver to perform the "basics" at a high level
-- connections, queries during cluster setup, things that don't
involve ABI changes. For new ABI I use ctypes, or as other people have
mentioned CFFI would work.
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-06-12 19:36:05 | Re: Addressing SECURITY DEFINER Function Vulnerabilities in PostgreSQL Extensions |
| Previous Message | Jacob Champion | 2024-06-12 19:33:53 | Re: RFC: adding pytest as a supported test framework |