Append the following lines in your settings: import sys if ‘test’ in sys.argv or ‘test_coverage’ in sys.argv: #Covers regular testing and django-coverage DATABASES[‘default’][‘ENGINE’] = ‘django.db.backends.sqlite3’ Make sure your actual database setting comes before them.
The code that doesn’t work: from django.contrib.auth.models import User from django.test import Client user = User.objects.create(username=”testuser”, password=’12345′) c = Client() logged_in = c.login(username=”testuser”, password=’12345′) Why doesn’t it work? In the snippet above, when the `User` is created the actual password hash is set to be `12345`. When the client calls the `login` method, the value … Read more
According to the mock documentation: Patch can be used as a TestCase class decorator. It works by decorating each test method in the class. This reduces the boilerplate code when your test methods share a common patchings set. This basically means that you can create a base test class with @patch decorator applied on it … Read more
This was an article I found helpful: A Guide to Testing in Django (archived link). Here is a good summary of what to test: Another common setback for developers/designers new to testing is the question of ‘what should (or shouldn’t) I test?’ While there are no hard & fast rules here that neatly apply everywhere, … Read more
I found this question when looking to disable a signal for a set of test cases and Germano’s answer lead me to the solution but it takes the opposite approach so I thought I’d add it. In your test class: class MyTest(TestCase): def setUp(self): # do some setup signals.disconnect(listener, sender=FooModel) Instead of adding decision code … Read more
The correct usage of Django (>= 1.4) test runner is as follows: import django, sys from django.conf import settings settings.configure(DEBUG=True, DATABASES={ ‘default’: { ‘ENGINE’: ‘django.db.backends.sqlite3′, } }, ROOT_URLCONF=’myapp.urls’, INSTALLED_APPS=(‘django.contrib.auth’, ‘django.contrib.contenttypes’, ‘django.contrib.sessions’, ‘django.contrib.admin’, ‘myapp’,)) try: # Django < 1.8 from django.test.simple import DjangoTestSuiteRunner test_runner = DjangoTestSuiteRunner(verbosity=1) except ImportError: # Django >= 1.8 django.setup() from django.test.runner import … Read more
Try passing the query parameter as a data payload instead. Change the line in your test to: response = self.client.get(‘/api/titles-and-blurbs/’, {‘genre’: ‘horror’}) Django docs here on the different ways to pass query parameters in urls. Another person reported a similar issue with an empty QUERY_PARAMS while testing DRF (see here). It looks like they fixed … Read more
Here’s how I did it: from django.test import Client import base64 auth_headers = { ‘HTTP_AUTHORIZATION’: ‘Basic ‘ + base64.b64encode(‘username:password’), } c = Client() response = c.get(‘/my-protected-url/’, **auth_headers) Note: You will also need to create a user.
See this solution: from django.utils import unittest from django.test.client import RequestFactory class SimpleTest(unittest.TestCase): def setUp(self): # Every test needs access to the request factory. self.factory = RequestFactory() def test_details(self): # Create an instance of a GET request. request = self.factory.get(‘/customer/details’) # Test my_view() as if it were deployed at /customer/details response = my_view(request) self.assertEqual(response.status_code, 200)
Since Django 1.3 there is a assertNumQueries available exactly for this purpose. One way to use it (as of Django 3.2) is as a context manager: # measure queries of some_func and some_func2 with self.assertNumQueries(2): result = some_func() result2 = some_func2()