From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Nikolay Shaplov <n(dot)shaplov(at)postgrespro(dot)ru> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PROPOSAL] TAP test example |
Date: | 2015-11-19 16:03:22 |
Message-ID: | 564DF2CA.5090305@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/19/15 9:57 AM, Tom Lane wrote:
>> >I wrote this example based on ssl TAP test. There was no DBI there. And I
>> >think it was done for purpose. If we add DBI to tests, then we should add it
>> >to build dependencies. And it is not a good idea, and so not a good example.
> Agreed. We aren't going to accept any core tests that depend on DBI/DBD.
> Now, that might be a fine example for tests written to test something that
> uses Postgres ... but not as an example of how to write a core test.
Isn't one of the goals of the TAP framework to be able to write SQL
level tests where we don't have to worry about random output changes,
like what line number on a script caused an error?
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-11-19 16:05:36 | Re: Re: In-core regression tests for replication, cascading, archiving, PITR, etc. |
Previous Message | Robert Haas | 2015-11-19 16:02:59 | Re: SPI and transactions |