From: | Noah Misch <noah(at)leadboat(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: RFC: adding pytest as a supported test framework |
Date: | 2024-06-11 23:48:29 |
Message-ID: | 20240611234829.9d@rfd.leadboat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 10, 2024 at 06:49:11PM -0700, Andres Freund wrote:
> On 2024-06-10 16:46:56 -0400, Andrew Dunstan wrote:
> > On 2024-06-10 Mo 16:04, Andres Freund wrote:
> > > Just for context for the rest the email: I think we desperately need to move
> > > off perl for tests. The infrastructure around our testing is basically
> > > unmaintained and just about nobody that started doing dev stuff in the last 10
> > > years learned perl.
> > 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.
>
> C is a a lot more useful to to them than perl. And it's actually far more
> widely known these days than perl.
If we're going to test in a non-Perl language, I'd pick C over Python. There
would be several other unlikely-community-choice languages I'd pick over
Python (C#, Java, C++). We'd need a library like today's Perl
PostgreSQL::Test to make C-language tests nice, but the same would apply to
any new language.
I also want the initial scope to be the new language coexisting with the
existing Perl tests. If a bulk translation ever happens, it should happen
long after the debut of the new framework. That said, I don't much trust a
human-written bulk language translation to go through without some tests
accidentally ceasing to test what they test in Perl today.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2024-06-12 00:49:20 | Re: Postgresql OOM |
Previous Message | David Christensen | 2024-06-11 22:54:34 | Re: Adding comments to help understand psql hidden queries |