There are many postgres unit testing libraries like pgtap, PGUnit and Epic.
But I think there might be some important things that are missing that makes using these tools easier, so I wrote pypgTAP project to make it easier at least for me to use these tools.
Here are the current issues that it solves for me:
1. Creates a throwaway postgres server that loads up pgTAP library ready for writing tests against and then spins it down.
2. Shares the python virtualenv of the client with the plpythonu stored procedures on the throwaway. This allows easier python code reuse.
3. Allows a user to discover a resources within his test directory for example for loading data for tests.
4. Multiple tests can be written in pure SQL with pgtap and transparently executed very easily.
How might I make it more useful for you?
1. What missing features prevents people from testing your SQL/psql in production that this tool might be enhanced with?
2. How do you maintain production code typically for postgres? For example, does the DataDefinition exist in projects in some VCS like git/svn/hg or does it exist as something managed by tools like Alembic; The latter can be a deal breaker for you using this tool, as it assumes DataDefinition along with DML code and its tests exist as physical files in a project directory.
3. Perhaps you want to plug in your own SQL libraries instead of pgTAP to write tests against?
-Regards
Sid
