Bird
Raised Fist0
Djangoframework~5 mins

Testing API endpoints in Django

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Introduction

Testing API endpoints helps ensure your web service works correctly and returns the right data. It catches errors early and keeps your app reliable.

When you want to check if your API returns the correct data for a request.
When you add new features to your API and want to make sure old parts still work.
When you fix bugs and want to confirm the problem is solved.
When you want to automate checks so you don’t have to test manually every time.
When you want to verify your API handles errors properly.
Syntax
Django
from django.test import TestCase
from rest_framework.test import APIClient

class YourApiTest(TestCase):
    def setUp(self):
        self.client = APIClient()

    def test_endpoint(self):
        response = self.client.get('/api/your-endpoint/')
        self.assertEqual(response.status_code, 200)
        self.assertIn('expected_key', response.json())

Use APIClient from Django REST Framework to simulate API calls.

Use assertEqual and other assertions to check response status and data.

Examples
Test a GET request that should return a list of items.
Django
def test_get_list(self):
    response = self.client.get('/api/items/')
    self.assertEqual(response.status_code, 200)
    self.assertIsInstance(response.json(), list)
Test a POST request to create a new item and check the response data.
Django
def test_post_create(self):
    data = {'name': 'Test Item', 'price': 10}
    response = self.client.post('/api/items/', data, format='json')
    self.assertEqual(response.status_code, 201)
    self.assertEqual(response.json()['name'], 'Test Item')
Test that requesting a non-existing item returns a 404 error.
Django
def test_404_not_found(self):
    response = self.client.get('/api/items/9999/')
    self.assertEqual(response.status_code, 404)
Sample Program

This test class checks three things: getting a list of items, creating a new item, and handling a request for an item that does not exist.

Django
from django.test import TestCase
from rest_framework.test import APIClient

class ItemApiTest(TestCase):
    def setUp(self):
        self.client = APIClient()

    def test_get_items_list(self):
        response = self.client.get('/api/items/')
        self.assertEqual(response.status_code, 200)
        self.assertIsInstance(response.json(), list)

    def test_create_item(self):
        data = {'name': 'Sample Item', 'price': 25}
        response = self.client.post('/api/items/', data, format='json')
        self.assertEqual(response.status_code, 201)
        self.assertEqual(response.json()['name'], 'Sample Item')

    def test_get_nonexistent_item(self):
        response = self.client.get('/api/items/9999/')
        self.assertEqual(response.status_code, 404)
OutputSuccess
Important Notes

Always use the setUp method to prepare your test client or data.

Use meaningful test method names starting with test_ so Django can find them.

Run tests often to catch problems early and keep your API working well.

Summary

Testing API endpoints helps keep your web service reliable and bug-free.

Use Django REST Framework's APIClient to simulate requests and check responses.

Write clear tests for different HTTP methods and expected results.

Practice

(1/5)
1. What is the main purpose of using Django REST Framework's APIClient in testing?
easy
A. To simulate API requests and check responses
B. To create database migrations automatically
C. To generate HTML templates for views
D. To manage user authentication in the admin panel

Solution

  1. Step 1: Understand the role of APIClient

    APIClient is designed to simulate HTTP requests to API endpoints in tests.
  2. Step 2: Identify its testing purpose

    It helps verify that the API sends correct responses to requests.
  3. Final Answer:

    To simulate API requests and check responses -> Option A
  4. Quick Check:

    APIClient simulates API calls [OK]
Hint: APIClient is for simulating API calls in tests [OK]
Common Mistakes:
  • Confusing APIClient with database migration tools
  • Thinking APIClient generates HTML templates
  • Assuming APIClient manages admin authentication
2. Which of the following is the correct way to import APIClient for testing in Django REST Framework?
easy
A. from django.test import APIClient
B. from rest_framework.test import APIClient
C. import APIClient from rest_framework
D. from rest_framework.client import APIClient

Solution

  1. Step 1: Recall the correct import path

    APIClient is part of rest_framework.test module.
  2. Step 2: Match the correct syntax

    The correct import is from rest_framework.test import APIClient.
  3. Final Answer:

    from rest_framework.test import APIClient -> Option B
  4. Quick Check:

    Correct import path [OK]
Hint: APIClient is in rest_framework.test module [OK]
Common Mistakes:
  • Importing APIClient from django.test instead
  • Using incorrect import syntax like 'import APIClient from ...'
  • Confusing module rest_framework.client with rest_framework.test
3. Given the following test code snippet, what will be the status code of the response if the endpoint exists and returns data successfully?
client = APIClient()
response = client.get('/api/items/')
print(response.status_code)
medium
A. 404
B. 302
C. 200
D. 500

Solution

  1. Step 1: Understand the GET request behavior

    A successful GET request to an existing API endpoint returns status code 200.
  2. Step 2: Identify the expected status code

    Since the endpoint exists and returns data, the status code will be 200.
  3. Final Answer:

    200 -> Option C
  4. Quick Check:

    Successful GET response = 200 [OK]
Hint: Successful GET requests return 200 status code [OK]
Common Mistakes:
  • Confusing 404 (not found) with success
  • Assuming 500 means success
  • Thinking 302 redirect is default for API GET
4. Identify the error in this test code snippet that causes the test to fail:
client = APIClient()
response = client.post('/api/items/', data={'name': 'Book'})
self.assertEqual(response.status_code, 201)
medium
A. Missing format='json' in the post request
B. Using post instead of get for data retrieval
C. Incorrect URL path format
D. Not importing APIClient before use

Solution

  1. Step 1: Check POST request data format

    By default, APIClient sends data as form-encoded unless format='json' is specified.
  2. Step 2: Understand why test fails

    The API expects JSON data, so missing format='json' causes the server to reject or misinterpret data, failing the test.
  3. Final Answer:

    Missing format='json' in the post request -> Option A
  4. Quick Check:

    POST JSON data needs format='json' [OK]
Hint: Add format='json' when posting JSON data [OK]
Common Mistakes:
  • Assuming POST sends JSON by default
  • Confusing GET and POST methods
  • Ignoring import statements
5. You want to test an API endpoint that requires authentication. Which sequence correctly tests a protected GET endpoint using Django REST Framework's APIClient?
hard
A. Call client.get() first, then authenticate client with credentials
B. Set authentication headers manually without using client methods
C. Use client.post() without authentication to access the endpoint
D. Authenticate client with credentials, then call client.get() on the endpoint

Solution

  1. Step 1: Authenticate the APIClient before requests

    Use client.force_authenticate(user=user) or set credentials before making requests.
  2. Step 2: Make the GET request after authentication

    Once authenticated, call client.get() to access the protected endpoint successfully.
  3. Final Answer:

    Authenticate client with credentials, then call client.get() on the endpoint -> Option D
  4. Quick Check:

    Authenticate before GET request [OK]
Hint: Authenticate client before calling protected endpoint [OK]
Common Mistakes:
  • Calling GET before authentication
  • Using POST instead of GET for retrieval
  • Manually setting headers incorrectly