| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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> |
| Subject: | Re: Direction for test frameworks: Perl TAP vs. Python/pytest |
| Date: | 2026-06-16 15:54:28 |
| Message-ID: | 15846444-57C0-416B-82FE-6FB5BE925537@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 16 Jun 2026, at 17:40, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
>> Even if we backpatch a new framework, we'd still need to port all the tests of
>> that release for it to be useful which seems like a pretty big hammer to swing.
>
> Agreed. But based on the quick count I just did, we are also going to
> need to deal with a lot of cases of modifying an existing test. If
> the "same" test is written completely differently in master, that's
> going to be super painful.
I'm afraid that you're right, and I 100% agree that any decision we make should
take ease-of-backpatching into strong consideration.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2026-06-16 15:54:34 | Re: Direction for test frameworks: Perl TAP vs. Python/pytest |
| Previous Message | Tom Lane | 2026-06-16 15:40:43 | Re: Direction for test frameworks: Perl TAP vs. Python/pytest |