heckyel/mediagoblin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Expect 404 in unit tests, if we now use 404.

Browse Source 
Our unit tests for auth were expecting a 400.
Well, now we give a 404. So expect that!

I'm not completely sure, if the 404 is the right thing
here, but that's another topic.
This commit is contained in:
Elrond 2011-12-02 00:09:13 +01:00
parent 8e2af2843f
commit 93e4622491
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
mediagoblin/tests/test_auth.py
View File

@ -280,16 +280,16 @@ def test_register_views(test_app):
template.clear_test_template_context()
response = test_app.get(
"/auth/forgot_password/verify/?userid=%s&token=total_bs" % unicode(
new_user._id), status=400)
assert response.status == '400 Bad Request'
new_user._id), status=404)
assert_equal(response.status, '404 Not Found')
## Try using an expired token to change password, shouldn't work
template.clear_test_template_context()
real_token_expiration = new_user['fp_token_expire']
new_user['fp_token_expire'] = datetime.datetime.now()
new_user.save()
response = test_app.get("%s?%s" % (path, get_params), status=400)
assert response.status == '400 Bad Request'
response = test_app.get("%s?%s" % (path, get_params), status=404)
assert_equal(response.status, '404 Not Found')
new_user['fp_token_expire'] = real_token_expiration
new_user.save()