| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| 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:40:43 |
| Message-ID: | 700264.1781624443@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 starting to think that we'd thank ourselves in the long run
if we did do the conversion in all branches at once.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2026-06-16 15:54:28 | Re: Direction for test frameworks: Perl TAP vs. Python/pytest |
| Previous Message | Tom Lane | 2026-06-16 15:31:47 | Re: Direction for test frameworks: Perl TAP vs. Python/pytest |