public inbox for [email protected]  

help / color / mirror / Atom feed

From: Noah Misch <[email protected]>
To: Andres Freund <[email protected]>
Cc: Andrew Dunstan <[email protected]>
Cc: Jacob Champion <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: RFC: adding pytest as a supported test framework
Date: Tue, 11 Jun 2024 16:48:29 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CAOYmi+kThkM9Z87u=R_Wi7fCor2i+UZKAyq0UCyprzCwTQvqgA@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>

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.

view thread (77+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: RFC: adding pytest as a supported test framework
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox