Re: Direction for test frameworks: Perl TAP vs. Python/pytest - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Direction for test frameworks: Perl TAP vs. Python/pytest
Date
Msg-id CAOYmi+k5odvXry42m=XyUyXyvrBrZc2CTMm4HNXNmVByHmuyZg@mail.gmail.com
Whole thread
In response to Re: Direction for test frameworks: Perl TAP vs. Python/pytest  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Direction for test frameworks: Perl TAP vs. Python/pytest
List pgsql-hackers
On Tue, Jun 16, 2026 at 9:02 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Once we feel
> that we have that pretty much down, we could think about converting
> the existing tests.  Based on this conversation, I think that step
> will probably need to touch the back branches too.

It would probably be pretty easy to do that in slices. Backport the
Python core, then develop the replacement for a segment of related
tests as a reviewable and backportable chunk. That lets us refactor
the testing APIs as we go, and if there are failures after backport,
at least it's just that one area of the tests and not "the whole
thing".

--Jacob



pgsql-hackers by date:

Previous
From: 신성준
Date:
Subject: Re: Add wait events for server logging destination writes
Next
From: Nathan Bossart
Date:
Subject: Re: Fix --missing-stats-only false positive for partitioned expression indexes