```

////

### 扩展后的测试文件

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

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

每当你需要客户端在请求中传递信息，但你不知道如何传递时，你可以通过搜索（谷歌）如何用 `httpx`做，或者是用 `requests` 做，毕竟HTTPX的设计是基于Requests的设计的。

接着只需在测试中同样操作。

示例：

* 传一个*路径* 或*查询* 参数，添加到URL上。
* 传一个JSON体，传一个Python对象(例如一个`dict`)到参数 `json`。
* 如果你需要发送 *Form Data* 而不是 JSON，使用 `data` 参数。
* 要发送 *headers*，传 `dict` 给 `headers` 参数。

            throws ArtifactResolutionException {
        List<ArtifactResult> results = new ArrayList<>();

        for (ArtifactRequest request : requests) {
            ArtifactResult result = new ArtifactResult(request);
            results.add(result);

            Artifact artifact = request.getArtifact();

	totalRequests := 0
	for _, v := range finalStats.TotalS3Requests.APIStats {
		totalRequests += v
	}
	if totalRequests == 0 {
		t.Error("Expected some total requests to be recorded, but got zero")
	}
	t.Logf("Total requests recorded: %d", totalRequests)
	t.Logf("Race condition test passed - no races detected")
}

// TestHTTPAPIStatsRaceCondition tests concurrent access to HTTPAPIStats specifically.

2. The client connects to the idle daemon and sends it a request to do some work. If the daemon is no longer running, the client starts again.
3. If the daemon is not able to run the request, for example it is already running a request or is shutting down, it rejects the request. The client starts again.
4. The daemon runs the request, sending back data such as logging output or tooling API events and intermediate models while doing so.

Sempre que você precisar que o cliente passe informações na requisição e não souber como, você pode pesquisar (no Google) como fazer isso no `httpx`, ou até mesmo como fazer isso com `requests`, já que o design do HTTPX é baseado no design do Requests.

Depois é só fazer o mesmo nos seus testes.

Por exemplo:

* Para passar um parâmetro *path* ou *query*, adicione-o à própria URL.

### CORS-запросы с предварительной проверкой { #cors-preflight-requests }

Это любые `OPTIONS`-запросы с заголовками `Origin` и `Access-Control-Request-Method`.

В этом случае middleware перехватит входящий запрос и отправит соответствующие CORS-заголовки в ответе, а также ответ `200` или `400` в информационных целях.

### Простые запросы { #simple-requests }

4. If you want *faster* PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
5. If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests
-->

#### What type of PR is this?

<!--
Add one of the following kinds:
/kind bug
/kind cleanup
/kind documentation

Check the docs about <a href="https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews" class="external-link" target="_blank">adding a pull request review</a> to approve it or request changes.

///

    about: Community support via Slack - for questions and discussions
  - name: MinIO Enterprise Support (SUBNET)
    url: https://min.io/pricing

///

### <a href="https://requests.readthedocs.io" class="external-link" target="_blank">Requests</a> { #requests }

**FastAPI** is not actually an alternative to **Requests**. Their scope is very different.

It would actually be common to use Requests *inside* of a FastAPI application.

But still, FastAPI got quite some inspiration from Requests.