Provide way to trigger an oops

[David Owen]

Provide ways to trigger oopses. One way should be a page to hit in a browser, which is protected by team membership, and another should be through the API (as it interacts with oops differently), also protected.

Related to bug #720607.

[Ricardo Kirkner (ricardokirkner)]

Ubuntu Pay has something for this; it's called poison. It consists of a middleware + some views that allow for generating errors anywhere in the code at runtime.

This should be extracted into a common application that can be shared by pay, sso and any other project.

[David Owen (dsowen)]

On Thu, 2011-02-17 at 17:47 +0000, Ricardo Kirkner wrote:
> Ubuntu Pay has something for this; it's called poison. It consists of a
> middleware + some views that allow for generating errors anywhere in the
> code at runtime.

Yes, Pay's poison is a cool system, but I was thinking (for this bug)
something much more simple: a single view that would do nothing except
raise an exception, every single time. The purpose would be to test the
oops machinery end-to-end.

I think it's also worth considering the injectable errors in the style
of Pay though.