| 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> |
| Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, <pgsql-hackers(at)postgresql(dot)org>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: 8.5 release timetable, again |
| Date: | 2009-08-27 14:07:05 |
| Message-ID: | 4A964CB9020000250002A3DE@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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....
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-08-27 14:11:24 | Re: 8.5 release timetable, again |
| Previous Message | Jean-Michel Pouré | 2009-08-27 14:05:26 | Re: MySQL Compatibility WAS: 8.5 release timetable, again |