-
Notifications
You must be signed in to change notification settings - Fork 24
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
Error message indistinguishable #132
Comments
@kevinetienne @meshy @Ian-Foote FYI |
Why do you need to distinguish between them? Is a 400 not enough to confirm your expected result? What are you testing exactly? |
It looks like we are already making the distinction between:
Maybe the first one should return a 401? |
@kevinetienne they are both bad requests. 400 is correct. |
@meshy I wanted to test two cases:
|
I think this might be trying to test too much in end-to-end tests. |
Possibly. |
I'm trying to e2e test user registration and login.
When I try to log in with bad credentials I get back a
400
error with a text innon_field_errors
Unable to log in with provided credentials.
When I try to log in with an unverified account I also get back a
400
error with a differentnon_field_errors
User account is disabled.
The only way to distinguish between them is by the error text, which will break when the text changes or we change to a different language.
A possible solution would be to use a different error status or maybe add a field which describes error type in machine readable form.
The text was updated successfully, but these errors were encountered: