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

From: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: Direction for test frameworks: Perl TAP vs. Python/pytest
Date: 2026-06-16 15:15:53
Message-ID: CAJ7c6TMxT7dCjzfzXpMB9VWSGwbZSPFAUcOa4TK+TpeuE19msw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Tom,

> I'm not super attracted to the idea of back-patching a whole new test
> framework into stable branches. But the alternatives are not pretty
> either --- eg, who will want to write a python test and then translate
> it to perl for the back branches?

That's a fair concern. It seems to me that back-patching TAP tests
doesn't happen too often. Also modern LLM agents should be quite good
at it.

--
Best regards,
Aleksander Alekseev

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2026-06-16 15:17:06 Re: [PATCH v1] Add ssl_alt_cert_file/ssl_alt_key_file for dual RSA+ECDSA certificate support
Previous Message Baji Shaik 2026-06-16 15:14:09 Re: [PATCH] COPY TO FORMAT json: respect column list order