Improve multiple schema testing

slaught commented 10 years ago

Trying to use pg_tapgen on a multischema database I ran into several issues.

Use full schema qualified names for objects and the associated pgtap functions.
Generate tests for Materialized Views and Foreign Tables. MV support is in head of pgtap, FT support is in a pending pull request.
Use plan() and include explicit count of tests in generated tests. This required rewriting the output routine but I work to minimize any changes to the output.
Removed the explicit setting of the search_path which is not a valid assumption for all databases. This removed a line of output.
Removed 'create extension' call. This causes more problems then it solves. You can't always install an extension on a postgres server where you can always just load a .sql file. Assume pgtap has been installed before test run.
Added support for connecting to databases with passwords using $PGPASSWORD. For example a Heroku postgres database always has a password.
Function list did not have an explicit ordering which resulted in output changes when no functions changed.
Bug Fix: Escape single quotes in column default values.

theory commented 8 years ago

This branch needs to be rebased onto theory/master. It was 11 commits behind when you forked it. Thanks!

slaught commented 8 years ago

@theory updated with master.

If you'd like or it is more helpful, I'll squash all the changes to a single commit and create a new prl.

theory commented 8 years ago

Yeah, would you? That'd be a big help.

theory / tap-parser-sourcehandler-pgtap