Re: RFC: adding pytest as a supported test framework

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Melanie Plageman <melanieplageman(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, 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-13 11:27:42
Message-ID: 285A718D-98E3-4F23-8ED2-75B4AA3F95A3@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 13 Jun 2024, at 00:34, Melanie Plageman <melanieplageman(at)gmail(dot)com> wrote:

> FWIW, I felt a lot of pain trying to write recovery TAP tests with
> IPC::Run's pumping functionality. It was especially painful (as
> someone who knows even less Perl than the "street fighting Perl"
> Thomas Munro has described having) before the additional test
> infrastructure was added in BackgroudPsql.pm last year.

A key aspect of this, which isn't specific to Perl or our use of it, is that
this was done in backbranches which doesn't have the (recently) much improved
BackgroundPsql.pm. The quality of our tools and the ease of use they provide
is directly related to the investment we make into continuously improving our
testharness. Regardless of which toolset we adopt, if we don't make this
investment (taking learnings from the past years and toolsets into account)
we're bound to repeat this thread in a few years advocating for toolset X+1.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2024-06-13 11:28:26 Re: Conflict Detection and Resolution
Previous Message Amit Kapila 2024-06-13 10:06:05 Re: Logical Replication of sequences