pytest-django for Django testing - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this pytest-django test?

Consider this Django model and pytest-django test. What will be the test result?

PyTest

from django.db import models

class Book(models.Model):
    title = models.CharField(max_length=100)

import pytest

@pytest.mark.django_db
def test_book_creation():
    book = Book.objects.create(title='Test Driven Development')
    assert Book.objects.count() == 1
    assert book.title == 'Test Driven Development'

A Test fails because assertion count is wrong

B Test fails because database access is not allowed

C Test raises AttributeError due to missing model

D Test passes successfully

💡 Hint

Remember to use @pytest.mark.django_db to allow database access in tests.

The test uses @pytest.mark.django_db which enables database access. The Book is created and counted correctly, so assertions pass.

❓ assertion

intermediate

Which assertion correctly checks the response status code in pytest-django?

You have a Django view that returns HTTP 200. Which assertion correctly verifies this in a pytest-django test?

PyTest

import pytest
from django.urls import reverse

@pytest.mark.django_db
def test_homepage(client):
    url = reverse('home')
    response = client.get(url)
    # Which assertion is correct here?

A assert response.status_code == 200

B assert response.code == 200

C assert response.status == 200

D assert response.status_code is '200'

💡 Hint

Check the attribute name for HTTP status code in Django test responses.

The correct attribute is response.status_code which holds an integer HTTP status code. Using '==' compares values correctly.

🔧 Debug

advanced

Why does this pytest-django test raise an error?

This test tries to create a Django user but raises an error. Identify the cause.

PyTest

import pytest
from django.contrib.auth.models import User

@pytest.mark.django_db
def test_create_user():
    user = User.objects.create(username='tester')
    assert User.objects.count() == 1
    assert user.username == 'tester'

# Error: django.db.utils.IntegrityError: NOT NULL constraint failed: auth_user.password

A Test fails because User model is not imported

B User creation fails because password field is required and missing

C Test fails because @pytest.mark.django_db is missing

D User creation fails because username is not unique

💡 Hint

Check required fields for Django's User model when creating users.

Django's User model requires a password field. Creating a user without password causes IntegrityError due to NOT NULL constraint.

❓ framework

advanced

Which pytest-django fixture provides a test client with database access?

You want to test Django views with database access in pytest. Which fixture should you use?

A django_client

B db_client

C client

D transactional_db_client

💡 Hint

pytest-django provides a built-in fixture for HTTP client with DB access.

The 'client' fixture in pytest-django provides a Django test client with database access enabled when @pytest.mark.django_db is used.

🧠 Conceptual

expert

What happens if you omit @pytest.mark.django_db in a test that accesses the database?

In pytest-django, what is the result of running a test that queries the database but does NOT have @pytest.mark.django_db?

A Test raises RuntimeError about database access not allowed

B Test runs successfully but database changes are not saved

C Test silently skips database queries

D Test raises django.core.exceptions.ImproperlyConfigured error

💡 Hint

pytest-django restricts database access unless explicitly allowed.

pytest-django raises a RuntimeError if a test accesses the database without @pytest.mark.django_db to prevent accidental DB usage.