Testing API endpoints in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the response status code for a successful GET request in Django REST Framework test?

Consider a Django REST Framework API endpoint tested with APIClient's get method. What status code should you expect for a successful GET request?

Django

from rest_framework.test import APIClient
client = APIClient()
response = client.get('/api/items/')

A 200

B 201

C 404

D 400

💡 Hint

A successful GET request usually returns a status code indicating success without creating new resources.

A successful GET request returns HTTP status code 200, meaning OK. Codes like 201 indicate resource creation, 400 is a bad request, and 404 means not found.

❓ state_output

intermediate

What is the value of response.data after posting valid data?

Given a Django REST Framework API test that posts valid data to create a new item, what will response.data contain?

Django

from rest_framework.test import APIClient
client = APIClient()
data = {'name': 'Test Item', 'price': 10.5}
response = client.post('/api/items/', data, format='json')

A {'error': 'Invalid data'}

B {'name': 'Test Item', 'price': 10.5}

C None

D {'id': 1, 'name': 'Test Item', 'price': 10.5}

💡 Hint

When a new item is created, the response usually includes the new item's ID along with the data sent.

After a successful POST, the response data includes the created item's fields plus its generated ID.

📝 Syntax

advanced

Which option correctly imports and uses APIClient in Django REST Framework tests?

Select the option that correctly imports APIClient and uses it to make a GET request in a Django test.

A

import APIClient from rest_framework.test
client = APIClient()
response = client.get('/api/data/')

B

from django.test import APIClient
client = APIClient()
response = client.get('/api/data/')

C

from rest_framework.test import APIClient
client = APIClient()
response = client.get('/api/data/')

D

from rest_framework.test import APIClient
client = APIClient
response = client.get('/api/data/')

💡 Hint

Check the correct import path and usage syntax for APIClient.

APIClient must be imported from rest_framework.test and instantiated with parentheses. Option C imports from wrong module, C has wrong import syntax, D forgets parentheses when instantiating.

🔧 Debug

advanced

Why does this test raise an AssertionError when checking response status?

This test expects status code 201 but fails. Why? from rest_framework.test import APIClient client = APIClient() data = {'title': 'New Post'} response = client.post('/api/posts/', data) assert response.status_code == 201

Django

from rest_framework.test import APIClient
client = APIClient()
data = {'title': 'New Post'}
response = client.post('/api/posts/', data)
assert response.status_code == 201

A The URL '/api/posts/' is incorrect and causes a 404 error.

B The post method needs format='json' to send JSON data; without it, the server rejects the data causing a 400 error.

C The data dictionary is missing required fields causing a 500 server error.

D The APIClient instance was not created properly causing a TypeError.

💡 Hint

Check how data is sent in POST requests with APIClient.

Without specifying format='json', APIClient sends data as form-encoded, which the API may reject, returning 400 instead of 201.

🧠 Conceptual

expert

Which option best describes the purpose of force_authenticate in DRF APIClient tests?

In Django REST Framework tests, what does the method force_authenticate do when used with APIClient?

A It forcibly sets the user on the client to simulate an authenticated request without performing actual login.

B It logs in the user by checking credentials against the database.

C It disables authentication checks for all requests made by the client.

D It resets the client's session to an anonymous user.

💡 Hint

Think about how tests simulate logged-in users without real login.

force_authenticate sets the user directly on the client to simulate authentication, bypassing login and token checks.