we have a suite of tests to ensure that a Pyramid app 'breaks' correctly. for example: if connectivity with Redis or a SqlAlchemy server is lost, there is some specific error processing and results handled via exception views; some other potential issues are handled via tweens.
the current approach to handling this is restarting the Pyramid app with certain connections turned off. we've been considering using a set of "testing-only" views, that trigger the exceptions with specific routes.
does anyone have insight/experience on this stuff they can share?