# 오버라이드로 의존성 테스트하기 { #testing-dependencies-with-overrides }

## 테스트 중 의존성 오버라이드하기 { #overriding-dependencies-during-testing }

테스트를 진행하다 보면 테스트 중에 의존성을 오버라이드해야 하는 경우가 있습니다.

원래 의존성을 실행하고 싶지 않을 수도 있습니다(또는 그 의존성이 가지고 있는 하위 의존성까지도 실행되지 않길 원할 수 있습니다).

대신, 테스트 동안(특정 테스트에서만) 사용될 다른 의존성을 제공하고, 원래 의존성이 사용되던 곳에서 사용할 수 있는 값을 제공하기를 원할 수 있습니다.

### 사용 사례: 외부 서비스 { #use-cases-external-service }

예를 들어, 외부 인증 제공자를 호출해야 하는 경우를 생각해봅시다.

# Classes as Dependencies { #classes-as-dependencies }

Before diving deeper into the **Dependency Injection** system, let's upgrade the previous example.

## A `dict` from the previous example { #a-dict-from-the-previous-example }

In the previous example, we were returning a `dict` from our dependency ("dependable"):

{* ../../docs_src/dependencies/tutorial001_an_py310.py hl[9] *}

# Dependency Olarak Class'lar { #classes-as-dependencies }

**Dependency Injection** sistemine daha derinlemesine geçmeden önce, bir önceki örneği geliştirelim.

## Önceki Örnekten Bir `dict` { #a-dict-from-the-previous-example }

Önceki örnekte, dependency'mizden ("dependable") bir `dict` döndürüyorduk:

{* ../../docs_src/dependencies/tutorial001_an_py310.py hl[9] *}

Ama sonra *path operation function* içindeki `commons` parametresinde bir `dict` alıyoruz.

接著，我們可以把上面的相依項（dependable）`common_parameters` 改成類別 `CommonQueryParams`：

{* ../../docs_src/dependencies/tutorial002_an_py310.py hl[11:15] *}

注意用來建立該類別實例的 `__init__` 方法：

{* ../../docs_src/dependencies/tutorial002_an_py310.py hl[12] *}

...它的參數與我們之前的 `common_parameters` 相同：

{* ../../docs_src/dependencies/tutorial001_an_py310.py hl[8] *}

**FastAPI** 會用這些參數來「解析」該相依性。

兩種情況下都會有：

- 一個可選的查詢參數 `q`，型別為 `str`。

name: Submit Dependency Graph
on:
  workflow_dispatch:
  push:
    branches:
      - master

permissions: {}

jobs:
  generate-and-submit:
    permissions:
      contents: write
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v6
    - uses: actions/setup-java@v5
      with:
        distribution: temurin
        java-version: 17
    - name: Setup Gradle

Although the hierarchical dependency injection system is very simple to define and use, it's still very powerful.

You can define dependencies that in turn can define dependencies themselves.

In the end, a hierarchical tree of dependencies is built, and the **Dependency Injection** system takes care of solving all these dependencies for you (and their sub-dependencies) and providing (injecting) the results at each step.

///

## Dependencies errors and return values { #dependencies-errors-and-return-values }

You can use the same dependency *functions* you use normally.

### Dependency requirements { #dependency-requirements }

They can declare request requirements (like headers) or other sub-dependencies:

{* ../../docs_src/dependencies/tutorial006_an_py310.py hl[8,13] *}

*Декоратор операции пути* получает необязательный аргумент `dependencies`.

Это должен быть `list` состоящий из `Depends()`:

{* ../../docs_src/dependencies/tutorial006_an_py310.py hl[19] *}

Зависимости из dependencies выполнятся так же, как и обычные зависимости. Но их значения (если они были) не будут переданы в *функцию операции пути*.

         * aftereffects and bogus error messages.
         */
        List<Dependency> dependencies = model.getDependencies();
        Map<String, Dependency> normalized = new LinkedHashMap<>(dependencies.size() * 2);

        for (Dependency dependency : dependencies) {
            normalized.put(dependency.getManagementKey(), dependency);
        }

        if (dependencies.size() != normalized.size()) {

///

## Dependency Hataları ve Return Değerleri { #dependencies-errors-and-return-values }

Normalde kullandığınız aynı dependency *function*'larını burada da kullanabilirsiniz.

### Dependency Gereksinimleri { #dependency-requirements }

Request gereksinimleri (header'lar gibi) veya başka alt dependency'ler tanımlayabilirler:

{* ../../docs_src/dependencies/tutorial006_an_py310.py hl[8,13] *}