Overriding dependencies in tests in FastAPI

Introduction

Sometimes you want to replace parts of your app with simple versions during tests. This helps you test without using real services or data.

You want to test an API endpoint without calling a real database.

You need to simulate a user login without real authentication.

You want to check how your app behaves with fixed data instead of live data.

You want to speed up tests by skipping slow external services.

You want to isolate parts of your app to find bugs easily.

Syntax

FastAPI

app.dependency_overrides[original_dependency] = override_dependency

# After tests, clear overrides
app.dependency_overrides.clear()

original_dependency is the function or class your app normally uses.

override_dependency is your test version that returns fixed or mock data.

Examples

This replaces the real database connection with a test version during tests.

FastAPI

def get_db():
    # real database connection
    pass

def override_get_db():
    # test database or mock
    pass

app.dependency_overrides[get_db] = override_get_db

This makes the app always use a test user instead of real login.

FastAPI

def get_current_user():
    # real user authentication
    pass

def override_user():
    return {'username': 'testuser'}

app.dependency_overrides[get_current_user] = override_user

Sample Program

This example shows how to replace the real database connection with a test version. The test calls the endpoint and prints the response, which uses the overridden dependency.

FastAPI

from fastapi import FastAPI, Depends
from fastapi.testclient import TestClient

app = FastAPI()

def get_db():
    return "real database connection"

@app.get("/items/")
async def read_items(db=Depends(get_db)):
    return {"db": db}

# Override dependency for tests
def override_get_db():
    return "test database connection"

app.dependency_overrides[get_db] = override_get_db

client = TestClient(app)

def test_read_items():
    response = client.get("/items/")
    assert response.status_code == 200
    print(response.json())

# Run test function
test_read_items()

Important Notes

Always clear overrides after tests if you run multiple tests to avoid side effects.

Overrides let you test parts of your app without needing real external systems.

Summary

Override dependencies to replace real parts with test versions.

This helps isolate and speed up tests.

Use app.dependency_overrides to set and clear overrides.

Practice

1. What is the main purpose of overriding dependencies in FastAPI tests?

easy

A. To replace real dependencies with test versions for isolated testing

B. To speed up the server in production

C. To add new routes dynamically

D. To change the database schema automatically

Solution

1. Step 1: Understand dependency overriding concept

   Overriding dependencies allows replacing real parts like database or external services with test doubles.

2. Step 2: Identify the testing benefit

   This replacement isolates tests and makes them faster and more reliable.

3. Final Answer:

   To replace real dependencies with test versions for isolated testing -> Option A

4. Quick Check:

   Override dependencies = isolate tests [OK]

Hint: Override to isolate and speed tests, not for production changes [OK]

Common Mistakes:

• Thinking overrides speed up production
• Confusing overrides with adding routes
• Assuming overrides change database schema

2. Which of the following is the correct way to override a dependency in FastAPI for testing?

easy

A. app.override[original_dep] = test_dep

B. app.override_dependency(original_dep, test_dep)

C. app.dependency_overrides[original_dep] = test_dep

D. app.set_dependency_override(original_dep, test_dep)

Solution

1. Step 1: Recall FastAPI override syntax

   FastAPI uses the dictionary app.dependency_overrides to map original dependencies to test versions.

2. Step 2: Match correct syntax

   Assigning test_dep to app.dependency_overrides[original_dep] is the correct way.

3. Final Answer:

   app.dependency_overrides[original_dep] = test_dep -> Option C

4. Quick Check:

   Use dependency_overrides dict = A [OK]

Hint: Use app.dependency_overrides dictionary to override [OK]

Common Mistakes:

• Using non-existent methods like override_dependency
• Trying to assign to app.override
• Calling set_dependency_override which doesn't exist

3. Given this test code snippet, what will be the output of the test client call?

from fastapi import FastAPI, Depends
from fastapi.testclient import TestClient

app = FastAPI()

def get_number():
    return 10

@app.get("/number")
def read_number(num: int = Depends(get_number)):
    return {"number": num}

def override_get_number():
    return 42

app.dependency_overrides[get_number] = override_get_number

client = TestClient(app)
response = client.get("/number")
print(response.json())

medium

A. {"number": 42}

B. {"number": 10}

C. {"number": null}

D. RuntimeError due to dependency override

Solution

1. Step 1: Understand dependency override effect

   The original get_number returns 10, but it is overridden by override_get_number returning 42.

2. Step 2: Analyze the endpoint response

   The endpoint uses Depends(get_number), so it will receive 42 from the override.

3. Final Answer:

   {"number": 42} -> Option A

4. Quick Check:

   Override returns 42, so response = {"number": 42} [OK]

Hint: Override changes return value used by endpoint [OK]

Common Mistakes:

• Assuming original dependency runs despite override
• Expecting null instead of overridden value
• Thinking override causes runtime error

4. You wrote this test code but it raises an error. What is the likely cause?

app.dependency_overrides[get_data] = override_get_data

# test code runs here

app.dependency_overrides.clear()

Error: KeyError during test execution.

medium

A. Calling clear() removes all overrides, but test still uses them

B. Not resetting dependency_overrides before tests causes conflict

C. Using clear() on dependency_overrides dictionary is invalid

D. Overriding dependencies must be done inside a fixture or context manager

Solution

1. Step 1: Understand dependency_overrides lifecycle

   Overrides should be reset before each test to avoid conflicts from previous tests.

2. Step 2: Identify cause of the test error

   If dependency_overrides is not cleared before tests, leftover overrides cause unexpected errors.

3. Final Answer:

   Not resetting dependency_overrides before tests causes conflict -> Option B

4. Quick Check:

   Reset overrides before tests to avoid conflicts [OK]

Hint: Clear overrides before tests to prevent conflicts [OK]

Common Mistakes:

• Assuming clear() is invalid method
• Not using fixtures to manage overrides lifecycle
• Believing overrides persist safely across tests

5. You want to test an endpoint that depends on a database session. How do you correctly override the database dependency to use a test session only during tests?

hard

A. Use a global variable to switch between real and test sessions inside db_session

B. Replace the db_session function globally in your app code with test session

C. Call get_test_db_session inside the endpoint instead of using Depends

D. Set app.dependency_overrides[db_session] = get_test_db_session before tests and clear after

Solution

1. Step 1: Use dependency_overrides for test isolation

   Override the database session dependency only during tests to avoid affecting production code.

2. Step 2: Properly set and clear overrides

   Assign the test session function to app.dependency_overrides[db_session] before tests and clear it after tests.

3. Final Answer:

   Set app.dependency_overrides[db_session] = get_test_db_session before tests and clear after -> Option D

4. Quick Check:

   Override dependency only in tests, then clear [OK]

Hint: Override dependency only in tests, clear after [OK]

Common Mistakes:

• Replacing functions globally breaks production code
• Using global flags inside dependency is error-prone
• Calling test session inside endpoint breaks separation