What would be the accepted method to stop this from happening during mocked auth unit

I ended up using this snippet in my testing.py settings <div class="snippet-clipbo

Don't raise UserWarning 'No request passed to the backend' during tests about django-ratelimit-backend HOT 2 OPEN

brutasse commented on May 30, 2024 1

Don't raise UserWarning 'No request passed to the backend' during tests

from django-ratelimit-backend.

Comments (2)

scjody commented on May 30, 2024 2

This warning happens for us whenever we call self.client.login() during tests. Workaround:

from django.contrib.auth.models import AnonymousUser
from django.urls import reverse
from django.test import RequestFactory, TestCase

class SomethingTests(TestCase):
    def setUp(self):
        factory = RequestFactory()
        self.login_request = factory.get(reverse('login'))
        self.login_request.user = AnonymousUser

        super(TestCase, self).setUp()

    def test_method(self):
        self.client.login(username='user', password='pass', request=self.login_request)

from django-ratelimit-backend.

ciarancourtney commented on May 30, 2024 2

I ended up using this snippet in my testing.py settings

import warnings
# https://github.com/brutasse/django-ratelimit-backend/issues/41
warnings.filterwarnings('ignore', message="No request passed to the backend", category=UserWarning)

from django-ratelimit-backend.

Don't raise UserWarning 'No request passed to the backend' during tests about django-ratelimit-backend HOT 2 OPEN

Comments (2)

Related Issues (16)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent