Он автоматически найдёт все файлы и тесты, выполнит их и предоставит Вам отчёт о результатах тестирования.

Запустите тесты:

<div class="termy">

```console
$ pytest

================ test session starts ================
platform linux -- Python 3.6.9, pytest-5.3.5, py-1.8.1, pluggy-0.13.1
rootdir: /home/user/code/superawesome-cli/app
plugins: forked-1.1.3, xdist-1.31.0, cov-2.8.1
collected 6 items

---> 100%

        // Test with various session ID values
        long[] sessionIds = { 0L, 1L, Long.MAX_VALUE, Long.MIN_VALUE, -1L };

        for (long sessionId : sessionIds) {
            doNothing().when(messageBlock).setSessionId(sessionId);
            messageBlock.setSessionId(sessionId);
            verify(messageBlock).setSessionId(sessionId);
        }
    }

    @Test
    @DisplayName("Test reset method")

---> 100%
```

</div>

`pytest` 파일과 테스트를 자동으로 감지하고 실행한 다음, 결과를 보고할 것입니다.

테스트를 다음 명령어로 실행하세요.

<div class="termy">

```console
$ pytest

================ test session starts ================
platform linux -- Python 3.6.9, pytest-5.3.5, py-1.8.1, pluggy-0.13.1
rootdir: /home/user/code/superawesome-cli/app
plugins: forked-1.1.3, xdist-1.31.0, cov-2.8.1
collected 6 items

---> 100%

Es erkennt die Dateien und Tests automatisch, führt sie aus und berichtet Ihnen die Ergebnisse.

Führen Sie die Tests aus, mit:

<div class="termy">

```console
$ pytest

================ test session starts ================
platform linux -- Python 3.6.9, pytest-5.3.5, py-1.8.1, pluggy-0.13.1
rootdir: /home/user/code/superawesome-cli/app
plugins: forked-1.1.3, xdist-1.31.0, cov-2.8.1
collected 6 items

---> 100%

* Tareas en segundo plano en el mismo proceso.
* Eventos de inicio y apagado.
* Cliente de prueba basado en HTTPX.
* **CORS**, GZip, archivos estáticos, responses en streaming.
* Soporte para **Session y Cookie**.
* Cobertura de tests del 100%.
* code base completamente anotada con tipos.

## Funcionalidades de Pydantic { #pydantic-features }

                params.put("ID", e.getId());
                params.put("Query ID", e.getQueryId());
                params.put("Doc ID", e.getDocId());
                params.put("User Session ID", e.getUserSessionId());
                params.put("URL", e.getUrl());
                params.put("URL ID", e.getUrlId());
                params.put("Order", toNumberString(e.getOrder()));

    boolean isDfsConvertToFQDN();

    /**
     * Minimum protocol version
     *
     * Property {@code jcifs.smb.client.minVersion} (string, default SMB1)
     *
     * @see DialectVersion
     * @return minimum protocol version to use/allow
     * @since 2.1
     */
    DialectVersion getMinimumVersion();

    /**
     * Maximum protocol version
     *

labels.regex=Expression régulière
labels.regularName=Nom régulier
labels.replacement=Remplacement
labels.sessionId=ID de session
labels.sortOrder=Ordre de tri
labels.updatedBy=Mis à jour par
labels.updatedTime=Date de mise à jour
labels.urls=URL
labels.userAgent=Agent utilisateur
labels.username=Nom d'utilisateur
labels.value=Valeur
labels.versionNo=Numéro de version
labels.cronExpression=Planification

O código de saída, o fechamento automático da `Session` em:

{* ../../docs_src/dependencies/tutorial013_an_py310.py ln[19:21] *}

...seria executado depois que a resposta terminar de enviar os dados lentos:

{* ../../docs_src/dependencies/tutorial013_an_py310.py ln[30:38] hl[31:33] *}

Mas como `generate_stream()` não usa a sessão do banco de dados, não é realmente necessário manter a sessão aberta enquanto envia a resposta.

    protected void setUp() throws Exception {
        super.setUp();

        crawlerThread = new CrawlerThread();
        crawlerContext = new CrawlerContext();
        crawlerContext.sessionId = "test-session";
        crawlerContext.numOfThread = 1;
        crawlerContext.maxThreadCheckCount = 10;
        crawlerContext.maxDepth = 3;
        crawlerContext.maxAccessCount = 0;