[Answered ]-Unable to authenticate Client in test

by

1👍

I’ve been doing a bunch of tests recently and here’s how are all of mine create the user inside of the setup, like the block below, give that a shot.

class AddressesViewTest(TestCase):
    def setUp(self):
        self.username = "jrandomuser"
        self.password = "qwerty123"
        user = User.objects.create(username=self.username)
        user.set_password(self.password)
        user.save()

        self.client.login(username=self.username, password=self.password)
        Address.objects.create(name="White House", address1="1600 Pennsylvania Ave", city="Washington", state="DC", postal_code="37188"

    def test_addresses(self):
        response = self.client.get(reverse("addresses-list"))
        self.assertContains(response, '"name":"White House"')

And actually I don’t even login during the setUp because I want to make sure the view has a @login_required, so it do it in the test itself:

class AddressesViewTest(TestCase):
    def setUp(self):
        self.username = "jrandomuser"
        self.password = "qwerty123"
        user = User.objects.create(username=self.username)
        user.set_password(self.password)
        user.save()
        Address.objects.create(name="White House", address1="1600 Pennsylvania Ave", city="Washington", state="DC", postal_code="37188"

    def test_anonymous(self):
        response = testObj.client.get(reverse("addresses-list"))
        testObj.assertEqual(response.status_code, 302, 'address-list @login_required Missing')

    def test_addresses(self):
        self.client.login(username=self.username, password=self.password)
        response = self.client.get(reverse("addresses-list"))
        self.assertContains(response, '"name":"White House"')

From what I’ve noticed is that setUp is ran per test. So in my last example the user would be created for anonymous, deleted or reverted, created for test_addresses. So having the user outside of that block is probably leading to the user not being deleted/reverted which is leading to some funky behavior.
And I know the tests say it removed the db every single time, without the --keepdb flag, but I’m starting to doubt that.. cause I’ve been hitting some weird behavior and it’s only after I run the test back-to-back-to-back-to-back.. something is off forsure

👤Nealium

0👍

A friend with more experience put me onto what seems to be the right track, which is a setUpTestData class method, that gets called only once. I would not have thought of this myself because I imagined classmethod to be similar to static in .NET or Java, but apparently not; I have quite a bit more to learn here.

Mostly all test data creation not specific to a particular test ought to go in setUpTestData, also, he says.

This works:

from django.contrib.auth.models import User
from django.test import Client, TestCase
from django.urls import reverse
from eventsadmin.models import Address


class AddressesViewTest(TestCase):
    @classmethod
    def setUpTestData(cls):
        cls.user = User.objects.create(username="jrandomuser")
        cls.client = Client()
        Address.objects.create(name="White House", address1="1600 Pennsylvania Ave", city="Washington", state="DC", postal_code="37188")

    def setUp(self):
        self.client.force_login(self.user)

    def test_addresses(self):
        response = self.client.get(reverse("addresses-list"))
        self.assertContains(response, '"name":"White House"')

As @nealium points out, it also makes sense to move the call to login or force_login into the test if there are any tests where you don’t want the Client to be authenticated.

👤Don R

Leave a comment