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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
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:20:12
Message-ID: 755389.1781626812@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> writes:
> 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".

Makes sense.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2026-06-16 16:21:57 Re: mxid_score can become Infinity in pg_stat_autovacuum_scores
Previous Message Robert Haas 2026-06-16 16:14:25 Re: Improving the names generated for indexes on expressions