Re: Direction for test frameworks: Perl TAP vs. Python/pytest - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Direction for test frameworks: Perl TAP vs. Python/pytest
Date
Msg-id 15846444-57C0-416B-82FE-6FB5BE925537@yesql.se
Whole thread
In response to Re: Direction for test frameworks: Perl TAP vs. Python/pytest  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> On 16 Jun 2026, at 17:40, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Daniel Gustafsson <daniel@yesql.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




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Direction for test frameworks: Perl TAP vs. Python/pytest
Next
From: Jacob Champion
Date:
Subject: Re: Direction for test frameworks: Perl TAP vs. Python/pytest