Re: More business with $Test::Builder::Level in the TAP tests

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема Re: More business with $Test::Builder::Level in the TAP tests
Дата
Msg-id 378556bb-680b-aa04-9cd4-b98b0dbc300d@dunslane.net
обсуждение исходный текст
Ответ на Re: More business with $Test::Builder::Level in the TAP tests  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: More business with $Test::Builder::Level in the TAP tests  (Michael Paquier <michael@paquier.xyz>)
Список 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
asok() or is().
 


cheers



andrew

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




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Prabhat Sahu
Дата:
Сообщение: Corruption with IMMUTABLE functions in index expression.
Следующее
От: Tom Lane
Дата:
Сообщение: Re: EXPLAIN(VERBOSE) to CTE with SEARCH BREADTH FIRST fails