Re: RFC: adding pytest as a supported test framework - Mailing list pgsql-hackers

From Jelte Fennema-Nio
Subject Re: RFC: adding pytest as a supported test framework
Date
Msg-id CAGECzQSMQ_iBTLAXDNywaKUgCx9XgZk4rDL3TxVCP9bchz_qUg@mail.gmail.com
Whole thread Raw
In response to Re: RFC: adding pytest as a supported test framework  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Mon, 10 Jun 2024 at 22:47, Andrew Dunstan <andrew@dunslane.net> wrote:
> As for what up and coming developers learn, they mostly don't learn C either, and that's far more critical to what we
do.

I think many up and coming devs have at least touched C somewhere
(e.g. in university). And because it's more critical to the project
and also to many other low level projects, they don't mind learning it
so much if they don't know it yet. But I, for example, try to write as
few Perl tests as possible, because getting good at Perl has pretty
much no use to me outside of writing tests for postgres.

(I do personally think that official Rust support in Postgres would
probably be a good thing, but that is a whole other discussion that
I'd like to save for some other day)

> But let's not throw the baby out with the bathwater. Quite apart from anything else, a wholesale rework of the test
infrastructurewould make backpatching more painful.
 

Backporting test improvements to decrease backporting pain is
something we don't look badly upon afaict (Citus its test suite breaks
semi-regularly on minor PG version updates due to some slight output
changes introduced by e.g. an updated version of the isolationtester).



pgsql-hackers by date:

Previous
From: Jelte Fennema-Nio
Date:
Subject: Re: RFC: adding pytest as a supported test framework
Next
From: Robert Haas
Date:
Subject: Re: Track the amount of time waiting due to cost_delay