Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow the fake mode to be used during tests #29

Open
stvnrlly opened this issue Apr 26, 2017 · 1 comment
Open

Allow the fake mode to be used during tests #29

stvnrlly opened this issue Apr 26, 2017 · 1 comment

Comments

@stvnrlly
Copy link
Contributor

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?

@stvnrlly
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant