Re: Replacing TAP test planning with done_testing()
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: 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-11T20:28:00Z
Lists: pgsql-hackers
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 -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
Commits
-
Replace Test::More plans with done_testing
- 549ec201d613 15.0 landed