Re: More business with $Test::Builder::Level in the TAP tests
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Michael Paquier <michael@paquier.xyz>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-10-11T14:48:54Z
Lists: pgsql-hackers
On 10/10/21 7:18 AM, Michael Paquier wrote:
> On Fri, Oct 08, 2021 at 12:14:57PM -0400, Andrew Dunstan wrote:
>> I think we need to be more explicit about it, especially w.r.t. indirect
>> calls. Every subroutine in the call stack below where you want to error
>> reported as coming from should contain this line.
> Hmm. I got to think about that for a couple of days, and the
> simplest, still the cleanest, phrasing I can come up with is that:
> This should be incremented by any subroutine part of a stack calling
> test routines from Test::More, like ok() or is().
>
> Perhaps you have a better suggestion?
I would say:
This should be incremented by any subroutine which directly or indirectly calls test routines from Test::More, such as ok() or is().
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
Commits
-
Add more $Test::Builder::Level in the TAP tests
- d5ab331a339d 12.9 landed
- bab0ff2e44b7 13.5 landed
- d834ebcf2320 14.1 landed
- f9c4cb686800 15.0 landed
-
Add missing $Test::Builder::Level settings
- 73aa5e0cafd0 15.0 cited