import org.junit.jupiter.api.Nested;
import org.junit.jupiter.api.Test;

/**
 * Unit tests for the {@link SmbComReadAndXResponse} class.
 */
public class SmbComReadAndXResponseTest {

    private SmbComReadAndXResponse response;

    @BeforeEach
    public void setUp() {
        response = new SmbComReadAndXResponse();
    }

    @Test
    public void testConstructor() {

  @J2ktIncompatible
  public void testStringConverter_nullPointerTester() throws Exception {
    Converter<String, TestEnum> converter = Enums.stringConverter(TestEnum.class);
    NullPointerTester tester = new NullPointerTester();
    tester.testAllPublicInstanceMethods(converter);
  }

  public void testStringConverter_nullConversions() {
    Converter<String, TestEnum> converter = Enums.stringConverter(TestEnum.class);

Ele também inclui o que mudou, como as validações agora são mais corretas e rigorosas, possíveis ressalvas, etc.

Você pode lê-lo para entender melhor o que mudou.

## Testes { #tests }

Garanta que você tenha [testes](../tutorial/testing.md) para sua aplicação e que os execute na integração contínua (CI).

Assim, você pode fazer a atualização e garantir que tudo continua funcionando como esperado.

# 非同步測試 { #async-tests }

你已經看過如何使用提供的 `TestClient` 來測試你的 FastAPI 應用。到目前為止，你只看到如何撰寫同步測試，沒有使用 `async` 函式。

在測試中能使用非同步函式會很有用，例如當你以非同步方式查詢資料庫時。想像你想測試發送請求到 FastAPI 應用，然後在使用非同步資料庫函式庫時，驗證後端是否成功把正確資料寫入資料庫。

來看看怎麼做。

## pytest.mark.anyio { #pytest-mark-anyio }

若要在測試中呼叫非同步函式，測試函式本身也必須是非同步的。AnyIO 為此提供了一個好用的外掛，讓我們可以標示某些測試函式以非同步方式執行。

## HTTPX { #httpx }

即使你的 FastAPI 應用使用一般的 `def` 函式而非 `async def`，它在底層仍然是個 `async` 應用。

# Асинхронні тести { #async-tests }

Ви вже бачили, як тестувати ваші застосунки **FastAPI** за допомогою наданого `TestClient`. До цього часу ви бачили лише, як писати синхронні тести, без використання функцій `async`.

        } else {
            return getOtherLocation(key);
        }
    } // -- InputLocation getLocation( Object )

    /**
     * Gets the map of nested element locations within this location.
     *
     * @return a map of keys to InputLocation instances for nested elements, or null if none
     */
    public java.util.Map<Object, InputLocation> getLocations() {
        return locations;

///

### Créer un chemin d'accès pour tester { #create-a-path-operation-to-test-it }

Maintenant, pour pouvoir vérifier que tout fonctionne, créez un chemin d'accès :

{* ../../docs_src/custom_docs_ui/tutorial001_py310.py hl[36:38] *}

### Tester { #test-it }

import org.junit.jupiter.api.Nested;
import org.junit.jupiter.api.RepeatedTest;
import org.junit.jupiter.api.Test;
import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.Arguments;
import org.junit.jupiter.params.provider.MethodSource;
import org.junit.jupiter.params.provider.ValueSource;

@DisplayName("NegTokenInit SPNEGO Token Tests")
class NegTokenInitTest {

This way, its schema will show up in the API docs user interface:

<img src="/img/tutorial/dataclasses/image01.png">

## Dataclasses in Nested Data Structures { #dataclasses-in-nested-data-structures }

You can also combine `dataclasses` with other type annotations to make nested data structures.

import jcifs.internal.SMBProtocolDecodingException;

/**
 * Test class for NegotiateContextResponse interface and its implementations
 */
@ExtendWith(MockitoExtension.class)
class NegotiateContextResponseTest {

    @Mock
    private Configuration mockConfig;

    @Nested
    @DisplayName("PreauthIntegrityNegotiateContext Tests")
    class PreauthIntegrityNegotiateContextTest {