Overriding dependencies in tests in FastAPI - Step-by-Step Execution

Concept Flow - Overriding dependencies in tests

Define original dependency

↓

Create FastAPI app

↓

Use dependency in route

↓

Write test function

↓

Override dependency with test version

↓

Run test client request

↓

Check response uses overridden dependency

This flow shows how FastAPI uses a dependency in a route, then in tests, the dependency is replaced with a test version to control behavior.

Execution Sample

FastAPI

from fastapi import FastAPI, Depends
app = FastAPI()

def get_number():
    return 42

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

Defines a FastAPI app with a route that depends on a function returning 42.

Execution Table

Step	Action	Dependency Used	Request Result	Notes
1	App starts	get_number	N/A	Original dependency returns 42
2	Test starts	get_number	N/A	Prepare to override dependency
3	Override dependency with get_test_number	get_test_number	N/A	Test dependency returns 99
4	Test client sends GET /number	get_test_number	{"number": 99}	Response uses overridden dependency
5	Test ends	get_number	N/A	Dependency override removed

💡 Test finishes after verifying response uses overridden dependency

Variable Tracker

Variable	Start	After Override	After Test Request	Final
dependency_function	get_number (returns 42)	get_test_number (returns 99)	get_test_number (returns 99)	get_number (returns 42)

Key Moments - 2 Insights

Why does the test response show 99 instead of 42?

Because in step 3 of the execution_table, the original dependency get_number is overridden by get_test_number which returns 99, so the route uses the test version during the test request.

Does the original dependency stay overridden after the test?

No, as shown in step 5, the override is removed after the test ends, so the app uses the original dependency again.

Visual Quiz - 3 Questions

Look at the execution_table, what does the dependency_function return after override?

A 99

B None

C 42

D 0

💡 Hint

Check the 'After Override' column in variable_tracker for dependency_function

At which step does the test client send the GET request?

A Step 3

B Step 4

C Step 2

D Step 5

💡 Hint

Look at the 'Action' column in execution_table for when the test client sends the request

If the override was not removed after the test, what would happen?

A The app would always return 42

B The app would crash

C The app would always return 99

D The app would return None

💡 Hint

Refer to the 'Final' column in variable_tracker and step 5 in execution_table

Concept Snapshot

FastAPI lets you replace dependencies during tests.
Define your original dependency function.
In tests, override it with app.dependency_overrides.
Run test client requests using the overridden version.
After tests, remove overrides to restore original behavior.

Full Transcript

This visual execution shows how FastAPI dependencies can be overridden in tests. First, the app uses a dependency function that returns 42. During testing, this dependency is replaced with a test version returning 99. When the test client sends a request, the route uses the overridden dependency, so the response contains 99. After the test, the override is removed, restoring the original dependency. This allows controlled testing of routes depending on external or variable data.

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