0Pricing
FastAPI Backend Development Bootcamp · 강의

FastAPI 엔드포인트 통합 테스트

FastAPI의 `TestClient`로 요청을 시뮬레이션하여 API 엔드포인트에 대한 통합 테스트를 수행합니다.

FastAPI 엔드포인트 통합 테스트은(는) CoddyKit의 무료 FastAPI Backend Development Bootcamp 강의입니다. 이것은 4개 중 2번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 FastAPI Backend Development Bootcamp 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. FastAPI Backend Development Bootcamp 강의에는 총 4개의 강의가 포함되어 있습니다.

이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.

What is Integration Testing?

Welcome to integration testing! After learning about unit tests, it's time to see how different parts of your FastAPI application work together.

  • Unit tests check individual functions or components in isolation.
  • Integration tests verify that multiple components of your system interact correctly. For a FastAPI app, this means testing your API endpoints, checking if they handle requests, interact with dependencies, and return expected responses.

These tests ensure your API behaves as expected when all its pieces are connected.

Introducing FastAPI's TestClient

FastAPI provides a powerful tool called TestClient from fastapi.testclient. This client allows you to make HTTP requests to your FastAPI application without needing to run a live server.

  • It simulates requests directly in memory.
  • It's built on top of the popular httpx library.
  • It's perfect for quickly testing your API endpoints during development.

Let's see how to set it up!

Setting Up Your TestClient

To use TestClient, you first need to import your FastAPI application instance and then pass it to the TestClient constructor. This creates a client instance ready to send simulated requests.

Try running this example to see a basic setup:

from fastapi import FastAPI
from fastapi.testclient import TestClient

# 1. Define your FastAPI app
app = FastAPI()

# 2. Define a simple endpoint
@app.get("/hello")
async def read_hello():
    return {"message": "Hello Test!"}

# 3. Create a TestClient instance
client = TestClient(app)

# 4. Define a test function
def test_read_hello():
    # Use the client to make a GET request
    response = client.get("/hello")
    
    # Assertions to check the response
    assert response.status_code == 200
    assert response.json() == {"message": "Hello Test!"}
    print("Test Passed: /hello endpoint works!")

# This block makes the script runnable directly
if __name__ == "__main__":
    print("Running a simple test with TestClient...")
    test_read_hello()

Testing GET Requests

Making GET requests is straightforward. You simply call the .get() method on your TestClient instance, passing the path of the endpoint you want to test.

After making the request, you can access properties of the response object like .status_code and .json() to verify the outcome.

from fastapi import FastAPI
from fastapi.testclient import TestClient

app = FastAPI()

@app.get("/items/")
async def read_items():
    return [{"name": "Laptop"}, {"name": "Mouse"}]

client = TestClient(app)

def test_read_items():
    response = client.get("/items/")
    
    print(f"Status Code: {response.status_code}")
    print(f"Response JSON: {response.json()}")
    
    assert response.status_code == 200
    assert len(response.json()) == 2
    assert response.json()[0]["name"] == "Laptop"
    print("Test Passed: /items/ returns correct data!")

if __name__ == "__main__":
    print("Testing /items/ endpoint...")
    test_read_items()

Testing Path & Query Parameters

TestClient handles path and query parameters just like a real browser. Path parameters are included directly in the URL string, and query parameters can be added to the URL or passed via the params argument.

Using the params argument for query parameters is often cleaner and handles URL encoding automatically.

from fastapi import FastAPI
from fastapi.testclient import TestClient

app = FastAPI()

@app.get("/items/{item_id}")
async def read_item(item_id: int, q: str = None):
    if q:
        return {"item_id": item_id, "q": q}
    return {"item_id": item_id}

client = TestClient(app)

def test_read_item_with_query():
    # Path param 5, Query param q=hello
    response = client.get("/items/5", params={"q": "hello"})
    assert response.status_code == 200
    assert response.json() == {"item_id": 5, "q": "hello"}
    print("Test Passed: Path & Query params handled!")

def test_read_item_no_query():
    # Only path param 10
    response = client.get("/items/10")
    assert response.status_code == 200
    assert response.json() == {"item_id": 10}
    print("Test Passed: Path param only handled!")

if __name__ == "__main__":
    print("Testing path and query parameters...")
    test_read_item_with_query()
    test_read_item_no_query()

Testing POST Requests with JSON

For endpoints that expect a request body (like POST or PUT), you can pass a Python dictionary directly to the json argument of the client method. TestClient will automatically convert this dictionary into a JSON string and set the appropriate Content-Type header.

from fastapi import FastAPI
from pydantic import BaseModel
from fastapi.testclient import TestClient

app = FastAPI()

class Product(BaseModel):
    name: str
    price: float
    description: str | None = None

@app.post("/products/")
async def create_product(product: Product):
    return product

client = TestClient(app)

def test_create_product():
    product_data = {"name": "Widget", "price": 29.99}
    response = client.post(
        "/products/",
        json=product_data
    )
    assert response.status_code == 200
    assert response.json() == {"name": "Widget", "price": 29.99, "description": None}
    print("Test Passed: POST request with JSON body!")

if __name__ == "__main__":
    print("Testing POST request...")
    test_create_product()

Overriding Dependencies for Testing

One of FastAPI's most powerful testing features is the ability to easily override dependencies. This is crucial for integration tests where you might want to:

  • Mock external services (e.g., a payment gateway).
  • Use a test database instead of the production one.
  • Inject specific test data or configurations.

You can temporarily replace a dependency function with a different one using app.dependency_overrides.

Applying Dependency Overrides

To override a dependency, you assign your mock function to the original dependency function in the app.dependency_overrides dictionary. After your test, it's vital to clear these overrides to prevent them from affecting other tests.

Let's see how to replace a 'real' setting with a 'test' setting:

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

app = FastAPI()

# Our 'real' dependency function
def get_current_env():
    return "production"

@app.get("/environment/")
async def get_environment(env: str = Depends(get_current_env)):
    return {"current_environment": env}

client = TestClient(app)

def test_get_environment_default():
    response = client.get("/environment/")
    assert response.status_code == 200
    assert response.json() == {"current_environment": "production"}
    print("Default environment test passed!")

def test_get_environment_override():
    # Our mock dependency function for testing
    def override_get_current_env():
        return "test"
    
    # Apply the override
    app.dependency_overrides[get_current_env] = override_get_current_env
    
    response = client.get("/environment/")
    assert response.status_code == 200
    assert response.json() == {"current_environment": "test"}
    print("Overridden environment test passed!")
    
    # IMPORTANT: Clear overrides after the test
    app.dependency_overrides.clear()

if __name__ == "__main__":
    print("Testing dependency overrides...")
    test_get_environment_default()
    test_get_environment_override()

Ensuring Cleanup of Overrides

Failing to clear app.dependency_overrides can lead to 'leaky' tests, where an override from one test unintentionally affects subsequent tests. Always make sure to reset app.dependency_overrides, typically by setting it back to an empty dictionary or using .clear().

This ensures each test runs in a clean, predictable state.

Test Your Knowledge!

Which of the following statements about FastAPI's TestClient is TRUE?

Recap & Next Steps

Great job! You've learned how to perform integration tests on your FastAPI application:

  • We explored what integration testing is and why it's crucial.
  • You mastered setting up and using FastAPI's TestClient to simulate various HTTP requests.
  • We covered testing GET and POST requests, including handling path, query, and JSON body parameters.
  • You now understand how to effectively use dependency overrides to isolate and control your test environment.

These skills are essential for building robust and reliable FastAPI applications. Keep practicing, and you'll be writing comprehensive tests in no time!

자주 묻는 질문

“FastAPI 엔드포인트 통합 테스트” 강의는 무료인가요?

네 — “FastAPI 엔드포인트 통합 테스트” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 FastAPI Backend Development Bootcamp 강의 전체를 잠금 해제할 수 있습니다. FastAPI Backend Development Bootcamp 강의에는 총 4개의 강의가 포함되어 있습니다.

“FastAPI 엔드포인트 통합 테스트”에서 뭘 배우나요?

FastAPI의 `TestClient`로 요청을 시뮬레이션하여 API 엔드포인트에 대한 통합 테스트를 수행합니다. 브라우저에서 직접 실행하는 실습 코드로 FastAPI Backend Development Bootcamp을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

FastAPI Backend Development Bootcamp을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 FastAPI Backend Development Bootcamp은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 2번째 강의입니다.

“FastAPI 엔드포인트 통합 테스트” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 FastAPI Backend Development Bootcamp 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 FastAPI Backend Development Bootcamp 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

  1. Pytest를 활용한 단위 테스트
  2. FastAPI 엔드포인트 통합 테스트
  3. FastAPI 애플리케이션 디버깅
  4. FastAPI 테스트에서 종속성 모킹하기
← FastAPI Backend Development Bootcamp(으)로 돌아가기