Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mvLhe-0003Ox-NS for pgsql-hackers@arkaria.postgresql.org; Thu, 09 Dec 2021 15:51:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mvLhd-0003no-K9 for pgsql-hackers@arkaria.postgresql.org; Thu, 09 Dec 2021 15:51:25 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mvLhd-0003kS-9n for pgsql-hackers@lists.postgresql.org; Thu, 09 Dec 2021 15:51:25 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mvLhZ-0001BB-Km for pgsql-hackers@postgresql.org; Thu, 09 Dec 2021 15:51:24 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id BE0A55C0207; Thu, 9 Dec 2021 10:51:19 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Thu, 09 Dec 2021 10:51:19 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=FgWsCIyEFOTwgX2kHuxyTJoTy82aPLF/Z4H92g3za EM=; b=CPCxDAkz7dG+GFgndRvRmFik7hZ15mkMVRFJL2H9RYwYownmdqCcdCq42 XGb4HYLIK3Xm9q1AjrAqpWqRujkgpLNa/zfmmlmjdXOqYyLbm6unE5Fc9g/u93gA DVtVKa937gNY7vRibW+z21kjcF3X/r6JKzmsNokVwyOWUbwqULx7cjG6MeGsePUi zmWqxGhbyZzzglijTuN63ckjNynyO4q/nMJFem8k0ogqfp8mnh0JlYnpR2w1YbYY 7E4g5cdraJaXS8EUs/Fut+VHDA2kJt5VtuQAEDbb4gSlNk+pF9H9ulXLKE4A/JYB hk6vd/BWRZ1IKvY/3I7Rvquff5lwA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrkedtgdekvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvghtvghr ucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrh hprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeefjeegheetuefhveevudel ueeftdejteeiffetvdduhfdtieefgfeutedtveeggfenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 9 Dec 2021 10:51:18 -0500 (EST) Message-ID: Date: Thu, 9 Dec 2021 16:51:17 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.3.2 Subject: Re: Readd use of TAP subtests Content-Language: en-US To: Tom Lane , =?UTF-8?Q?Dagfinn_Ilmari_Manns=c3=a5ker?= Cc: Andrew Dunstan , Daniel Gustafsson , pgsql-hackers References: <9878e1e2-2ce3-6df0-3498-07d967534f5e@enterprisedb.com> <87zgpbnr59.fsf@wibble.ilmari.org> <6131CFD1-EC47-41ED-999E-AB28B40DDEAA@yesql.se> <87wnkfnq9m.fsf@wibble.ilmari.org> <7e67b831-9eae-cd19-c96c-c1e59d916498@dunslane.net> <87tufjnodg.fsf@wibble.ilmari.org> <3662434.1638984660@sss.pgh.pa.us> From: Peter Eisentraut In-Reply-To: <3662434.1638984660@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 08.12.21 18:31, Tom Lane wrote: > A question that seems pretty relevant here is: what exactly is the > point of using the subtest feature, if we aren't especially interested > in its effect on the overall test count? I can see that it'd have > value when you wanted to use skip_all to control a subset of a test > run, but I'm not detecting where is the value-added in the cases in > Peter's proposed patch. It's useful if you edit a test file and add (what would appear to be) N tests and want to update the number. But I'm also OK with the done_testing() style, if there are no drawbacks to that. Does that call into question why we raised the Test::More version to begin with? Or were there other reasons?