When testing browser interactions, the test user may need to log in. Running through the real UAA process isn't really possible, but the fake mode is. Since tests set DEBUG=False, however, the current setup requires things to run through the real UAA.
I do appreciate the check for production mode, so maybe a separate flag for test mode is possible? Or maybe the solution is to mock the authentication and not worry about this module at all?