liveBook · Manning

Django test client

As explained in Django in Action

The Django test client is a test utility that simulates requests to a Django application and supports authentication and HTTP method calls.

The Django test client lets a test interact with a Django application without opening a browser. It sends GET and POST requests through URL routing, renders templates, and returns a response containing the status code, rendered content, and template context. JavaScript does not run, so this is a fast way to test server-side behavior rather than full browser interaction. section 8.2

Testing the credits view

A minimal test uses Django's TestCase and its client object: from django.test import TestCase class TestHome(TestCase): def test_credits(self): response = self.client.get("/credits/") self.assertEqual(200, response.status_code) The call travels through the URL router to the view. The assertion then checks that the view returned HTTP 200. Run it with `python manage.py test`; Django creates the test database, runs the test, and destroys that database afterward. section 8.2

Use the client to exercise more realistic request paths:

  • Call `client.post()` with a dictionary of form data, including file handles for upload tests. section 8.10
  • Call `client.login()` after creating a test user to visit authentication-protected pages. section 8.10
  • Check negative cases such as a 404 response, not only successful status codes. section 8.10

How Django in Action covers it

How deep it goes
Covers GET, POST, authentication, uploads, responses, and negative cases, but stops short of executing JavaScript or browser interaction.
Examples
Uses the credits view, GET and POST requests, status assertions, authenticated pages, 404 checks, and uploaded files.
What it assumes
Assumes basic Django views and URL routing, while demonstrating the test class, request calls, assertions, and test command from the beginning.
What you can do after
Apply it via Django TestCase to verify view responses and exercise unauthenticated, authenticated, invalid, and upload request paths.
How it connects
Connects Django TestCase, URL routing, HTTP responses, templates, authentication, file uploads, and assertions.
Cover of Django in Action
liveBookmanning.com
Read Django in Action on liveBook Get the book at manning.com

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Django in Action. The section links point to the parts of the book it draws on.