-
Notifications
You must be signed in to change notification settings - Fork 102
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
Make tests pass on Django==1.7 #20
Comments
I get this error:
This is because our manage.py is importing models (225e89f) before django is set up. I added a
|
Why are those lines there in the first place? You could potentially sidestep this by creating an app that is only installed during test runs and put that monkepatch code in the |
They're needed to run the tests on django 1.6. I don't remember exactly why, maybe @rockymeza does. |
It was issue #12 |
I profoundly do not understand what happened in #12. |
I also get the auth_customuser error and I don't know where it's coming from. I think that maybe it's time we stop relying on the built-in tests. |
My stuff is in the 1.7-support branch, but I'm stuck on the same error as @gavinwahl was. |
The django.contrib.auth tests have their own models, but where are the migrations? How do those models get created in django's tests? I think that part is just getting skipped when we run the tests. |
@gavinwahl @rockymeza This models get created without migrations in Django tests à la You can run the tests, but they don't pass. I'm still working on it. |
The code seems to work as far as I can tell.
The text was updated successfully, but these errors were encountered: