Django test RequestFactory vs Client Django test RequestFactory vs Client django django

Django test RequestFactory vs Client


RequestFactory and Client have some very different use-cases. To put it in a single sentence: RequestFactory returns a request, while Client returns a response.

The RequestFactory does what it says - it's a factory to create request objects. Nothing more, nothing less.

The Client is used to fake a complete request-response cycle. It will create a request object, which it then passes through a WSGI handler. This handler resolves the url, calls the appropriate middleware, and runs the view. It then returns the response object. It has the added benefit that it gathers a lot of extra data on the response object that is extremely useful for testing.

The RequestFactory doesn't actually touch any of your code, but the request object can be used to test parts of your code that require a valid request. The Client runs your views, so in order to test your views, you need to use the Client and inspect the response. Be sure to check out the documentation on the Client.


When using Django REST framework request factory would be helpfull to test the permissions.

EX:

Class TestPermission(TestCase):      def test_admin_permisiion(self):        admin_user = User.objects.create(email='admin@gmail.com',password='admin997',is_staff=True)        factory = RequestFactory()        request = factory.get('/')        request.user = admin_user        permission = IsAdminUser()        has_permission = permission.has_permission(request, None)        self.assertTrue(has_permission)

what we have done hear is we created a admin user by setting is_staff=True , then we created a request and assigned the admin as user of the request. request factory helps us do so. then we checked the IsAdminUser() permission from DRF against the request. the test will pass .

Client is to be used when you need to test the response returned by an Api.