Re: Direction for test frameworks: Perl TAP vs. Python/pytest

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, Aleksander Alekseev <aleksander(at)tigerdata(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Melanie Plageman <melanieplageman(at)gmail(dot)com>
Subject: Re: Direction for test frameworks: Perl TAP vs. Python/pytest
Date: 2026-06-16 16:11:32
Message-ID: CAOYmi+k5odvXry42m=XyUyXyvrBrZc2CTMm4HNXNmVByHmuyZg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 16, 2026 at 9:02 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

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