Skip site navigation (1) Skip section navigation (2)

Re: [pgsql-hackers] Daily digest v1.9418 (15 messages)

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Kevin(dot)Grittner(at)wicourts(dot)gov
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [pgsql-hackers] Daily digest v1.9418 (15 messages)
Date: 2009-08-27 16:07:31
Message-ID: f67928030908270907m4e7df1f2lfa03d12a6d6ed957@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
>
> ---------- Forwarded message ----------
> From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
> To: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Bruce Momjian" <
> bruce(at)momjian(dot)us>
> Date: Thu, 27 Aug 2009 09:07:05 -0500
> Subject: Re: 8.5 release timetable, again
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> > Maybe we should be looking at an expanded test suite that runs on a
> > time scale of hours rather than seconds.
>
> > if we could say that we had a regression test suite which covered X%
> > of our code, and it passed on all Y platforms tested, that would
> > certainly be a confidence booster, especially for large values of X.
>
> > Part of the question, of course, is how to build up such a
> > regression test suite.
>
> Aren't there code coverage monitoring tools that could be run during
> regression tests?  Sure it would take some time to review the results
> and fashion tests to exercise chunks of code which were missed, but at
> least we could quantify X and try to make incremental progress on
> increasing it....


But the fact that a piece of code was executed doesn't mean
it did the right thing.  If it does something subtly wrong,
will we notice?


Jeff

Responses

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2009-08-27 16:10:45
Subject: Re: [pgsql-hackers] Daily digest v1.9418 (15 messages)
Previous:From: Tom LaneDate: 2009-08-27 16:04:54
Subject: Re: Patches for static check on geo_ops.c

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group