The assert I mentioned in comment #2 should probably go. I think it was added to track down disconnection errors we were seeing (and have now been fixed in Storm).
http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/view/head:/lib/canonical/librarian/tests/test_db_outage.py has tests for how the Librarian handles an outage. A similar approach should be doable to bring up an appserver connected via pgbouncer. If it is a problem, I was toying with the idea of installing the pgbouncer fixture once for everything and running all tests through it.
The assert I mentioned in comment #2 should probably go. I think it was added to track down disconnection errors we were seeing (and have now been fixed in Storm).
http:// bazaar. launchpad. net/~launchpad- pqm/launchpad/ devel/view/ head:/lib/ canonical/ librarian/ tests/test_ db_outage. py has tests for how the Librarian handles an outage. A similar approach should be doable to bring up an appserver connected via pgbouncer. If it is a problem, I was toying with the idea of installing the pgbouncer fixture once for everything and running all tests through it.