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 1muypi-0004Tn-7K for pgsql-hackers@arkaria.postgresql.org; Wed, 08 Dec 2021 15:26:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1muypB-0001fM-JX for pgsql-hackers@arkaria.postgresql.org; Wed, 08 Dec 2021 15:25:41 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1muypB-0001fD-9z for pgsql-hackers@lists.postgresql.org; Wed, 08 Dec 2021 15:25:41 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1muyp9-0005nq-0w for pgsql-hackers@postgresql.org; Wed, 08 Dec 2021 15:25:40 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 1B8FPWaK3654397; Wed, 8 Dec 2021 10:25:32 -0500 From: Tom Lane To: Andrew Dunstan cc: =?UTF-8?Q?Dagfinn_Ilmari_Manns=c3=a5ker?= , Daniel Gustafsson , Peter Eisentraut , pgsql-hackers Subject: Re: Readd use of TAP subtests In-reply-to: <7e67b831-9eae-cd19-c96c-c1e59d916498@dunslane.net> 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> Comments: In-reply-to Andrew Dunstan message dated "Wed, 08 Dec 2021 09:33:06 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <3654395.1638977132.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Wed, 08 Dec 2021 10:25:32 -0500 Message-ID: <3654396.1638977132@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrew Dunstan writes: > On 12/8/21 09:08, Dagfinn Ilmari Mannsåker wrote: >> Either way, I think we should be switching tests to done_testing() >> whenever it would otherwise have to adjust the test count, to avoid >> having to do that again and again and again going forward. > I'm not so sure. I don't think its necessarily a bad idea to have to > declare how many tests you're going to run. I think the main point is to make sure that the test script reached an intended exit point, rather than dying early someplace. It's not apparent to me why reaching a done_testing() call is a less reliable indicator of that than executing some specific number of tests --- and I agree with ilmari that maintaining the test count is a serious PITA. regards, tom lane