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

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Gustafsson <daniel(at)yesql(dot)se>, 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>, Melanie Plageman <melanieplageman(at)gmail(dot)com>
Subject: Re: Direction for test frameworks: Perl TAP vs. Python/pytest
Date: 2026-06-16 23:06:49
Message-ID: CAOYmi+=WHS+ZnD34_2TgtpdOpuaZTh_WNc3zmPnfYXjKE=V3=g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 16, 2026 at 4:02 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> The only thing I'd argue to avoid is having to maintain two versions
> of the same test across *two* infrastructures.

I think that's a reasonable requirement.

--Jacob

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-06-16 23:23:08 Re: 004_timeline_switch TAP test may fail
Previous Message Michael Paquier 2026-06-16 23:02:13 Re: Direction for test frameworks: Perl TAP vs. Python/pytest