From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Writing new unit tests with PostgresNode |
Date: | 2016-02-23 01:52:08 |
Message-ID: | CAB7nPqRQZ+6+M9i+YyQFUhNDAhkCbGMGWcVDw8qfo6UA0C216w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Feb 23, 2016 at 12:29 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Craig Ringer wrote:
>
>> > +=pod
>> > +
>> > +=head2 Set up a node
>> > pod format... Do we really want that? Considering that those modules
>> > are only aimed at being dedicated for in-core testing, I would say no.
>>
>> If it's plain comments you have to scan through massive piles of verbose
>> Perl to find what you want. If it's pod you can just perldoc
>> /path/to/module it and get a nice summary of the functions etc.
>>
>> If these are intended to become usable facilities for people to write tests
>> with then I think it's important that the docs be reasonably accessible.
>
> Yes, I think adding POD here is a good idea. I considered doing it
> myself back when I was messing with PostgresNode ...
OK, withdrawal from here. If there are patches to add that to the
existing tests, I'll review them, and rebase what I have depending on
what gets in first. Could a proper patch split be done please?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Vitaly Burovoy | 2016-02-23 01:54:05 | Re: [PATH] Correct negative/zero year in to_date/to_timestamp |
Previous Message | Jim Nasby | 2016-02-23 01:32:14 | Re: format() changes discussion (was: Re: psql metaqueries with \gexec) |