You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
It looks like it's possible to indirectly use the test client's force_login() by grabbing the session cookie and adding it into Selenium, so this might be a non-issue.
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?
The text was updated successfully, but these errors were encountered: