Re: [HACKERS] PostgreSQL unit tests

2006-02-23 Thread Michael Glaesemann
On Feb 24, 2006, at 13:25 , Gavin Sherry wrote: On Feb 23, 2006, at 11:40 , Gavin Sherry wrote: I do think that unit testing of areas such as data types would be useful, particularly the date/time code and arrays as I consider that area of the code quite fragile. I wouldn't expect the unit t

Re: [HACKERS] PostgreSQL unit tests

2006-02-23 Thread Gavin Sherry
On Fri, 24 Feb 2006, Michael Glaesemann wrote: > [I neglected to cc the list in my reply earlier. Apologies to Gavin > for the double-post.] > > On Feb 23, 2006, at 11:40 , Gavin Sherry wrote: > > > > I do think that unit testing of areas such as data types would be > > useful, > > particularly t

Re: [HACKERS] PostgreSQL unit tests

2006-02-23 Thread Michael Glaesemann
[I neglected to cc the list in my reply earlier. Apologies to Gavin for the double-post.] On Feb 23, 2006, at 11:40 , Gavin Sherry wrote: I do think that unit testing of areas such as data types would be useful, particularly the date/time code and arrays as I consider that area of the c

Re: [HACKERS] PostgreSQL unit tests

2006-02-22 Thread Jim C. Nasby
On Thu, Feb 23, 2006 at 01:40:06PM +1100, Gavin Sherry wrote: > I previously proposed integrating a unit test framework into PostgreSQL. > Getting started wasn't much fun and I gave up. This is because unit > testing is really suited to a functional programming model, IMHO. Testing > the most compl

Re: [HACKERS] PostgreSQL unit tests

2006-02-22 Thread Gavin Sherry
On Wed, 22 Feb 2006, Alvaro Herrera wrote: > Robert Treat wrote: > > > You could check into what spikesource has been doing. I believe they mostly > > just piggyback off of our regression tests for postgresql core, but there > > might still be something that could be built upon. If you look at t

Re: [HACKERS] PostgreSQL unit tests

2006-02-22 Thread Alvaro Herrera
Robert Treat wrote: > You could check into what spikesource has been doing. I believe they mostly > just piggyback off of our regression tests for postgresql core, but there > might still be something that could be built upon. If you look at this url > http://developer.spikesource.com/spikewa

Re: [HACKERS] PostgreSQL unit tests

2006-02-22 Thread Tom Lane
Michael Glaesemann <[EMAIL PROTECTED]> 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

Re: [HACKERS] PostgreSQL unit tests

2006-02-22 Thread Robert Treat
On Wednesday 22 February 2006 01:27, Michael Glaesemann wrote: > During Josh Berkus' presentation at the JPUG PostgreSQL Conference, I > was particularly struck by the fact that 8.1 had a shorter beta > period than previous releases, rolled out on time, and enjoyed a > longer period before the firs

Re: [HACKERS] PostgreSQL unit tests

2006-02-22 Thread Andrew Dunstan
Lukas Smith wrote: Michael Glaesemann wrote: During Josh Berkus' presentation at the JPUG PostgreSQL Conference, I was particularly struck by the fact that 8.1 had a shorter beta period than previous releases, rolled out on time, and enjoyed a longer period before the first post-release bu

Re: [HACKERS] PostgreSQL unit tests

2006-02-21 Thread Lukas Smith
Michael Glaesemann wrote: During Josh Berkus' presentation at the JPUG PostgreSQL Conference, I was particularly struck by the fact that 8.1 had a shorter beta period than previous releases, rolled out on time, and enjoyed a longer period before the first post-release bug was reported. The Post

[HACKERS] PostgreSQL unit tests

2006-02-21 Thread Michael Glaesemann
During Josh Berkus' presentation at the JPUG PostgreSQL Conference, I was particularly struck by the fact that 8.1 had a shorter beta period than previous releases, rolled out on time, and enjoyed a longer period before the first post-release bug was reported. The PostgreSQL Build Farm play