Horton

Re: Replacing TAP test planning with done_testing()

Julien Rouhaud <rjuju123@gmail.com>

View thread View on postgr.es
From: Julien Rouhaud <rjuju123@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>, Daniel Gustafsson <daniel@yesql.se>, Michael Paquier <michael@paquier.xyz>, Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-02-12T02:06:03Z
Lists: pgsql-hackers 
Le sam. 12 févr. 2022 à 04:28, Alvaro Herrera <alvherre@alvh.no-ip.org> a
écrit :

> On 2022-Feb-11, Tom Lane wrote:
>
> > Andres Freund <andres@anarazel.de> writes:
>
> > > +1 on backpatching. Backpatching tests now is less likely to cause
> conflicts,
> > > but more likely to fail during tests.
> >
> > If you've got the energy to do it, +1 for backpatching.  I agree
> > with Michael's opinion that doing so will probably save us
> > future annoyance.
>
> +1
>

+1

>

Commits

  1. Replace Test::More plans with done_testing