Robert Haas <robertmh...@gmail.com> writes:
> On Mon, Nov 9, 2015 at 2:02 AM, Craig Ringer <cr...@2ndquadrant.com> wrote:
>> Something that'd really help with that, IMO, would be weakening the
>> requirement that everything be C or be core Perl. Instead require that
>> configure detect whether or not facilities for some tests are present,
>> and have them fail with a clean warning indicating they were skipped
>> for lack of pre-requisites at 'make' time.
> I actually kind of hate this sort of thing.
FWIW, I agree with Robert's position. Expanding the infrastructure
required for tests may make life simpler for the initial author of a test,
but we pay for that over and over again when you consider the long run.
I think insisting on having e.g. DBD::Pg is simply exporting the author's
work to other people; there isn't anything that that enables that you
can't do without it. We have added test infrastructure when there simply
wasn't any other way to test something. Both the isolation framework and
the TAP framework represent substantial investments of that sort. I'm
fine with both of those. But the bar to adding new requirements ought to
be pretty darn high, and not just "I was too lazy to write it without".
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
