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? -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/caf7e2b9-1dd9-4105-baaf-630ae37cfe27%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
