Re: PostgreSQL unit tests

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Glaesemann <grzm(at)myrealbox(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PostgreSQL unit tests
Date: 2006-02-22 14:53:45
Message-ID: 11558.1140620025@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Glaesemann <grzm(at)myrealbox(dot)com> writes:
> Something that has been briefly discussed in the past wrt PostgreSQL
> has been unit testing to complement the current regression tests.

I was and remain pretty dubious of this idea. In the backend in
particular, there is very little code that could usefully be tested
in a stand-alone fashion. For instance, almost everything assumes
the presence of palloc and elog and related facilities, and most
things depend at some level on having catalog data, and there are
lots of complicated, frequently-changed data structures involved in
the APIs. I think you'd spend vastly more time constructing and
maintaining unit-test cases than would ever be repaid :-(

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2006-02-22 15:08:59 Request: set opclass for generated unique and primary key indexes
Previous Message Mark Woodward 2006-02-22 14:22:14 Re: pg_config, pg_service.conf, postgresql.conf ....