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

Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> writes:
> On Tue, Jun 16, 2026 at 8:41 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'm starting to think that we'd thank ourselves in the long run
>> if we did do the conversion in all branches at once.

> Avoiding the "big bang" port was one of the reasons I proposed adding
> a Python suite that only does things we don't currently do in Perl (a
> pared-down option B, plus Test::Session). That way, we shake out the
> Python deployment/maintenance questions and begin to develop a shared
> vocabulary *before* the entirety of the test suite starts depending on
> it.

There's definitely a lot to be said for having an initial phase where
only all-new test scripts get written in Python, and we shake out the
test infrastructure's teething problems in master only. 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.

regards, tom lane