...
```

#### What is OpenAPI for { #what-is-openapi-for }

The OpenAPI schema is what powers the two interactive documentation systems included.

And there are dozens of alternatives, all based on OpenAPI. You could easily add any of those alternatives to your application built with **FastAPI**.

     */
    protected EditBody createEditBody(final KuromojiItem entity, final String dictId) {
        final EditBody body = new EditBody();
        body.id = entity.getId();
        body.dictId = dictId;
        body.token = entity.getToken();
        body.reading = entity.getReading();
        body.pos = entity.getPos();
        body.segmentation = entity.getSegmentation();
        return body;
    }

│   ├── __init__.py
│   ├── main.py
│   └── test_main.py
```

假設現在你的 **FastAPI** 應用所在的 `main.py` 有一些其他的路徑操作（path operations）。

它有一個可能回傳錯誤的 `GET` 操作。

它有一個可能回傳多種錯誤的 `POST` 操作。

兩個路徑操作都需要一個 `X-Token` 標頭（header）。

{* ../../docs_src/app_testing/app_b_an_py310/main.py *}

### 擴充的測試檔案 { #extended-testing-file }

接著你可以把 `test_main.py` 更新為擴充後的測試：

{* ../../docs_src/app_testing/app_b_an_py310/test_main.py *}

.
├── app
│   ├── __init__.py
│   ├── main.py
│   └── test_main.py
```

假设现在包含**FastAPI** app的文件 `main.py` 有些其他**路径操作**。

有个 `GET` 操作会返回错误。

有个 `POST` 操作会返回一些错误。

所有*路径操作* 都需要一个`X-Token` 头。

{* ../../docs_src/app_testing/app_b_an_py310/main.py *}

### 扩展后的测试文件 { #extended-testing-file }

然后您可以使用扩展后的测试更新`test_main.py`：

{* ../../docs_src/app_testing/app_b_an_py310/test_main.py *}

以下是一些包在 HTML「abbr」元素中的內容（部分為杜撰）：

### abbr 提供完整詞組 { #the-abbr-gives-a-full-phrase }

* <abbr title="Getting Things Done - 搞定工作法">GTD</abbr>
* <abbr title="less than - 小於"><code>lt</code></abbr>
* <abbr title="XML Web Token - XML 網路權杖">XWT</abbr>
* <abbr title="Parallel Server Gateway Interface - 平行伺服器閘道介面">PSGI</abbr>

### abbr 提供完整詞組與說明 { #the-abbr-gives-a-full-phrase-and-an-explanation }

const DefaultSkewTime = 15 * time.Minute

// validateStorageRequestToken will validate the token against the provided audience.
func validateStorageRequestToken(token string) error {
	claims := xjwt.NewStandardClaims()
	if err := xjwt.ParseWithStandardClaims(token, claims, []byte(globalActiveCred.SecretKey)); err != nil {
		return errAuthentication
	}

    discussion_number: int | None = None,
    discussion_id: str | None = None,
    comment_id: str | None = None,
    body: str | None = None,
) -> dict[str, Any]:
    headers = {"Authorization": f"token {settings.github_token.get_secret_value()}"}
    variables = {
        "after": after,
        "category_id": category_id,
        "discussion_number": discussion_number,
        "discussion_id": discussion_id,

Ele tem uma operação `GET` que pode retornar um erro.

Ele tem uma operação `POST` que pode retornar vários erros.

Ambas as *operações de rotas* requerem um cabeçalho `X-Token`.

{* ../../docs_src/app_testing/app_b_an_py310/main.py *}

### Arquivo de teste estendido { #extended-testing-file }

Você pode então atualizar `test_main.py` com os testes estendidos:

We see that we are going to need some dependencies used in several places of the application.

So we put them in their own `dependencies` module (`app/dependencies.py`).

We will now use a simple dependency to read a custom `X-Token` header:

{* ../../docs_src/bigger_applications/app_an_py310/dependencies.py hl[3,6:8] title["app/dependencies.py"] *}

/// tip

We are using an invented header to simplify this example.

        // Act + Assert (no exception expected)
        assertDoesNotThrow(() -> SmbCopyUtil.copyFile(src, dest, buffers, 1, new WriterThread(), sh, dh));

        // Verify that server-side path engaged at least the initial opens
        verify(src, times(1)).openUnshared(anyInt(), anyInt(), anyInt(), anyInt(), anyInt());
        verify(dest, times(1)).openUnshared(anyInt(), anyInt(), anyInt(), anyInt(), anyInt());
    }