Crie funções com um nome que comece com `test_` (essa é a convenção padrão do `pytest`).

Use o objeto `TestClient` da mesma forma que você faz com `httpx`.

Escreva instruções `assert` simples com as expressões Python padrão que você precisa verificar (novamente, `pytest` padrão).

{* ../../docs_src/app_testing/tutorial001_py310.py hl[2,12,15:18] *}

/// tip | Dica

Observe que as funções de teste são `def` normais, não `async def`.

---
jjbb-template: periodic-trigger-lgc.yml
vars:
  - periodic-job: elastic+elasticsearch+%BRANCH%+periodic+packaging-tests
  - lgc-job: elastic+elasticsearch+%BRANCH%+intake

---
- job:
    name: elastic+elasticsearch+%BRANCH%+multijob+third-party-tests-geoip
    workspace: /dev/shm/elastic+elasticsearch+%BRANCH%+multijob+third-party-tests-geoip
    display-name: "elastic / elasticsearch # %BRANCH% - third party tests geoip"
    description: "Testing of the Elasticsearch %BRANCH% third party tests against GeoIP database service\n"
    builders:
      - inject:
          properties-file: '.ci/java-versions.properties'

---
- job:
    name: elastic+elasticsearch+%BRANCH%+multijob+third-party-tests-azure
    workspace: /dev/shm/elastic+elasticsearch+%BRANCH%+multijob+third-party-tests-azure
    display-name: "elastic / elasticsearch # %BRANCH% - third party tests azure"
    description: "Testing of the Elasticsearch %BRANCH% third party tests against Azure\n"
    builders:
      - inject:
          properties-file: '.ci/java-versions.properties'
          properties-content: |

    "groups" : [ {
      "testProject" : "largeJavaMultiProject",
      "comment" : "We only test the multi-project here since for the monolithic project we would have no cache hits. This would mean we actually would test incremental compilation.",
      "coverage" : {
        "per_commit" : [ "linux" ]
      }
    } ]
  }, {

---
jjbb-template: periodic-trigger-lgc.yml
vars:
  - periodic-job: elastic+elasticsearch+%BRANCH%+periodic+third-party-tests
  - lgc-job: elastic+elasticsearch+%BRANCH%+intake

    }

    @Test
    public void test_store_withValidData() {
        // Prepare test data
        DataStoreParams paramMap = new DataStoreParams();
        Map<String, Object> dataMap = new HashMap<>();
        dataMap.put("url", "http://example.com/test");
        dataMap.put("title", "Test Document");

        // Execute

      - name: Generate test class runtime JSON
        run: |
          cd /tmp/gradle-ci-health
          ./gradlew :run --args "/tmp/test-class-data.json ${GITHUB_WORKSPACE}"
      - name: Update test bucket split
        run: |
          cd ${GITHUB_WORKSPACE}/.teamcity
          ./mvnw compile exec:java@update-test-buckets -DinputTestClassDataJson=/tmp/test-class-data.json

Yuri Schimke <******@****.***> 1703342811 +0000

#!/bin/bash

# This script is used to test the migration of IAM content from old minio
# instance to new minio instance.
#
# To run it locally, start the LDAP server in github.com/minio/minio-iam-testing
# repo (e.g. make podman-run), and then run this script.
#
# This script assumes that LDAP server is at:
#
#   `localhost:389`
#
# if this is not the case, set the environment variable
# `_MINIO_LDAP_TEST_SERVER`.