In order to check if user is authentcated in test, you can run:
from django.contrib.auth import get_user
class MyTestCase(TestCase):
def test_login(self):
self.assertFalse(get_user(self.client).is_authenticated())
self.client.login(username='fred', password='secret')
self.assertTrue(get_user(self.client).is_authenticated())Subscribe for the news and updates
This article offers key insights into the ISTQB certification and shares a proven preparation strategy to help candidates succeed.
One of the key requirements for modern UI is being performant. No matter how beautiful your app looks and what killer features it offers, it will frustrate your users if it clangs.
Dive into our guide to RESTful API best practices
Protection of WEB App is of paramount importance and it should be afforded the same level of security as the intellectual rights or private property. I'm going to cover how to protect your web app.
It appears that not everyone knows that in python you can create classes dynamically without metaclasses. I'll show an example of how to do it.So we've learned how to use custom QuerySet to chain requests:Article.objects.old().public()Now we need to make it work for related objects:user.articles.old().public()This is done using use_for_related_fields, but it needs a little trick.
In my current project I had a task to use twitter API. Twitter uses OAuth for authentication, which is pretty dreary. To avoid fiddling with it all the time, I've moved authentication to decorator. If key is available - nothing happens, just view is launched as usual. It's convenient that there's no need for additional twitter settings in user profile. Code is in article.