Re: [COMMITTERS] pgsql: Add TAP tests for client programs

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [COMMITTERS] pgsql: Add TAP tests for client programs
Date: 2014-04-16 03:03:11
Message-ID: 534DF2EF.5080808@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 4/14/14, 10:30 PM, Andrew Dunstan wrote:
>
> On 04/14/2014 10:17 PM, Tom Lane wrote:
>> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>>> Add TAP tests for client programs
>> I assume the buildfarm would need to be taught about this?
>>
>>
>
>
> Yes. It probably won't be a huge change, but it will need a bit of code.

It might be more future-proof if the build farm just called make
check-world and used some other way to identify the individual tests in
that output. Otherwise, we'll need a new build farm release every time
a test suite is added.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2014-04-16 03:11:05 Re: [COMMITTERS] pgsql: Add TAP tests for client programs
Previous Message Tom Lane 2014-04-15 19:34:40 Re: test script, was Re: [COMMITTERS] pgsql: psql: conditionally display oids and replication identity

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-04-16 03:11:05 Re: [COMMITTERS] pgsql: Add TAP tests for client programs
Previous Message Amit Kapila 2014-04-16 02:51:14 Re: PostgreSQL in Windows console and Ctrl-C