Regression tests

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: Postgres Hackers List <hackers(at)postgresql(dot)org>
Subject: Regression tests
Date: 2000-01-06 07:01:01
Message-ID: 38743DAD.6A651D27@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

OK, I've updated most of the regression tests to match the new psql
output conventions. Several of the tests at the end, starting with
"join", currently fail on my test setup, but that is probably because
I've got a few changes in for "outer join syntax" which are not
sufficient to avoid crashes. It might be good for someone to run the
regression test and hand-inspect the tests which fail to verify that
it is just a formatting difference and not the "backend closed
connection" I'm seeing here.

Once I've got a bit more code done, I'll come back to the regression
tests. If someone wants to finish up the regression test updates, then
the only thing remaining is to do the following:

1) run the regression test (hey, that "parallel testing" looks
interesting btw; thanks Jan!)

2) cd results

3) For each of the failed tests at the end,
diff -w <testfile.out> ../expected/ | less
(if differences are not in the query results)
cp -p <testfile.out> ../expected/

3') There may be one or two "expected" files coming from ../output/;
it isn't that complicated to get those updated, involving copying the
results file to ../output/ and then modifying the file path names.

4) Commit the changed "expected" files to CVS

- Thomas

--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Mount 2000-01-06 10:04:45 RE: [HACKERS] Source code format vote
Previous Message The Hermit Hacker 2000-01-06 05:31:27 Re: [HACKERS] UdmSearch: tables vs indices ...