Message-ID: <726c3a72-b6b2-ae0f-7d69-86bd2a5f5a2a@dunslane.net>
Date: Wed, 8 Dec 2021 08:53:59 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.2.0
Subject: Re: Readd use of TAP subtests
Content-Language: en-US
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
 pgsql-hackers <pgsql-hackers@postgresql.org>
References: <9878e1e2-2ce3-6df0-3498-07d967534f5e@enterprisedb.com>
From: Andrew Dunstan <andrew@dunslane.net>
In-Reply-To: <9878e1e2-2ce3-6df0-3498-07d967534f5e@enterprisedb.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/726c3a72-b6b2-ae0f-7d69-86bd2a5f5a2a%40dunslane.net>
Precedence: bulk


On 12/8/21 08:26, Peter Eisentraut wrote:
>
> Now that subtests in TAP are supported again, I want to correct the
> great historical injustice of 7912f9b7dc9e2d3f6cd81892ef6aa797578e9f06
> and put those subtests back.
>
> Much more work like this is possible, of course.  I just wanted to get
> this out of the way since the code was already written and I've had
> this on my list for, uh, 7 years.


+many as long as we cover all the cases in Cluster.pm and Utils.pm. I
suspect they have acquired some new multi-test subs in the intervening 7
years :-)


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com