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

Changed test_emails to use selenium. #191

Closed

Conversation

chris-leach
Copy link
Contributor

This fixes an issue that was causing password reset tests to pass when run alone, but fail when the whole test suite was run.

@mikebryant
Copy link
Contributor

Why doesn't the normal test client work for this?
Selenium shouldn't be required to test a simple view...

@chris-leach
Copy link
Contributor Author

I'm still unsure. The email backend seems to fail completely silently, and I've been unable to find anyone else with the same issue, but

  1. this is definitely the test that causes the others to fail.
  2. this is the only test in the suite that currently uses the default client - all the rest use selenium.

@mikebryant
Copy link
Contributor

I believe this is superseded by #192

@mikebryant mikebryant closed this Jul 6, 2016
@chris-leach chris-leach deleted the fix-interfering-tests branch July 7, 2016 09:04
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

Successfully merging this pull request may close these issues.

None yet

2 participants