Overriding dependencies in tests in FastAPI - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of overriding dependencies in FastAPI tests?

Overriding dependencies lets you replace real parts of your app (like database or authentication) with test versions. This helps test specific parts safely and predictably.

beginner

How do you override a dependency in FastAPI during testing?

Use the app.dependency_overrides dictionary to assign a new function that returns test data instead of the real dependency.

intermediate

Why should you clear dependency overrides after tests?

Clearing overrides prevents test dependencies from affecting other tests or the app when running normally, keeping tests isolated and reliable.

beginner

Example: What does this code do? app.dependency_overrides[get_db] = override_get_db

It tells FastAPI to use override_get_db instead of get_db whenever get_db is needed. This is usually done in tests to provide a fake or test database session.

intermediate

Can you override dependencies that use async functions in FastAPI tests?

Yes, you can override async dependencies by providing async functions as overrides. FastAPI supports async and sync dependencies equally.

What is the main reason to override dependencies in FastAPI tests?

A To replace real parts with test versions for controlled testing

B To speed up the app in production

C To add new features to the app

D To change the app's URL paths

Overriding dependencies allows tests to use controlled, fake versions of parts like databases, making tests reliable and safe.

How do you tell FastAPI to use a test version of a dependency?

A By editing the database config file

B By changing the main.py file directly

C By restarting the server

D By modifying app.dependency_overrides with the test function

You assign the test function to app.dependency_overrides for the original dependency key.

What should you do after finishing tests that override dependencies?

A Change the app version

B Clear the overrides to avoid side effects

C Restart the computer

D Leave them as is for next tests

Clearing overrides keeps tests isolated and prevents unexpected behavior in other tests or app runs.

Can you override async dependencies in FastAPI tests?

A No, only sync functions can be overridden

B Only if you use a special library

C Yes, by providing async functions as overrides

D Only in production, not tests

FastAPI supports async dependencies and you can override them with async functions in tests.

Which dictionary holds the overrides for dependencies in FastAPI?

A app.dependency_overrides

B app.dependencies

C app.override_dependencies

D app.test_dependencies

The app.dependency_overrides dictionary is used to map original dependencies to their test overrides.

Explain how to override a database dependency in FastAPI tests and why it is useful.

Think about replacing real parts with test versions for safe testing.

Describe the steps to safely use dependency overrides in multiple FastAPI tests.

Consider setup and cleanup in testing.

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