Make admin_user & admin_client fixtures compatible with custom user models #885
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The previous test setup inherited from AbstractUser thus MyCustomUser still had a username field. The problems people are having when using the admin_client fixture in combination with a custom user model are due to the username field not being present. This change accounts for the more realistic scenario.
Relying on `User.USERNAME_FIELD` is enough for light customization and doesn't require `extra_arguments`. Esoteric user models probably need a specially tailored manager anyway and most likely a custom `django_user` fixture that goes with that.
bluetech
force-pushed
the
jnns-admin-client-fix
branch
from
7a8716f to
c7f27cb
Compare
|
It turns out mysql has some restriction on the max_size of unique indexes, so I lowered the EmailField max_size from 254 to 100. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replaces PR #843 with some minor updates. Commits by @jnns.
Using the
admin_clientfixture with a custom user model that doesn't have a username field doesn't work currently. The fixture assumes that the user model always has ausernamefield present. For this case, Django hasUser.USERNAME_FIELDandUser.get_username().Unfortunately, the existing test didn't catch this issue because a custom user model with
User.usernameis used.This pull request changes the test setup to use a custom user without
usernameand makesadmin_clientuseUser.get_username().There are a few merge requests and issues about this problem already. I hope this one meets the requirements to be merged. If not, please let me know and I see what I can do.
Closes #246
Closes #484
Closes #748
Fixes #457