@Test
    @DisplayName("Test isDFSSupported returns false")
    void testIsDFSSupportedFalse() {
        // Arrange
        when(negotiationResponse.isDFSSupported()).thenReturn(false);

        // Act
        boolean result = negotiationResponse.isDFSSupported();

        // Assert
        assertFalse(result);
        verify(negotiationResponse).isDFSSupported();
    }

    @Test

        JvmVendor vendor = runtimeJdkMetaData.getVendor();
        return runtimeJdkMetaData.getVendor().getKnownVendor().name() + "/" + vendor.getRawVendor();
    }

    /* Introspect all versions of ES that may be tested against for backwards
     * compatibility. It is *super* important that this logic is the same as the
     * logic in VersionUtils.java. */
    private static BwcVersions resolveBwcVersions(File root) {

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

---
- job:
    name: "elastic+elasticsearch+pull-request+packaging-tests-windows-sample"
    display-name: "elastic / elasticsearch - pull request packaging-tests-windows-sample"
    description: "Testing of Elasticsearch pull requests - packaging-tests-windows-sample"
    # We use a hard-coded workspace directory here to avoid hitting windows path length limits
    child-workspace: "C:\\Users\\jenkins\\workspace\\pr-packaging-windows\\${BUILD_NUMBER}"

dataclass는 자동으로 Pydantic dataclass로 변환됩니다.

이렇게 하면 해당 스키마가 API docs 사용자 인터페이스에 표시됩니다:

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

## 중첩 데이터 구조에서 Dataclasses 사용하기 { #dataclasses-in-nested-data-structures }

`dataclasses`를 다른 타입 애너테이션과 조합해 중첩 데이터 구조를 만들 수도 있습니다.

일부 경우에는 Pydantic 버전의 `dataclasses`를 사용해야 할 수도 있습니다. 예를 들어 자동 생성된 API 문서에서 오류가 발생하는 경우입니다.

        assertNotNull(result);
        assertTrue(result.contains("null"));
        assertTrue(result.endsWith("\n"));
    }

    @Test
    public void test_execute_withNestedExceptionCause() {
        // Setup mock SearchLogHelper that throws nested exception
        SearchLogHelper mockSearchLogHelper = new SearchLogHelper() {
            @Override
            public void storeSearchLog() {

import java.util.jar.Manifest;
import java.util.logging.Logger;
import java.util.zip.ZipEntry;
import junit.framework.TestCase;
import org.jspecify.annotations.NullUnmarked;
import org.junit.Test;

/** Functional tests of {@link ClassPath}. */
@NullUnmarked
public class ClassPathTest extends TestCase {
  private static final Logger log = Logger.getLogger(ClassPathTest.class.getName());

* More advanced (but equally easy) techniques for declaring **deeply nested JSON models** (thanks to Pydantic).
* **GraphQL** integration with [Strawberry](https://strawberry.rocks) and other libraries.
* Many extra features (thanks to Starlette) as:
    * **WebSockets**
    * extremely easy tests based on HTTPX and `pytest`
    * **CORS**
    * **Cookie Sessions**
    * ...and more.

        assertEquals(rootCause, exception.getCause().getCause());
    }

    @Test
    public void test_exceptionSerialization() {
        // Test that the exception is serializable
        String message = "Serialization test";
        Exception cause = new Exception("Test cause");

        SearchQueryException exception = new SearchQueryException(message, cause);

---
- job:
    name: "elastic+elasticsearch+pull-request+packaging-tests-unix-sample"
    display-name: "elastic / elasticsearch - pull request packaging-tests-unix-sample"
    description: "Testing of Elasticsearch pull requests - packaging-tests-unix-sample"
    project-type: matrix
    node: master
    scm:
      - git:
          refspec: "+refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/*"
          branches: