* @throws PACDecodingException if the PAC decoding fails.
     */
    @Test
    void testIsCredentialTypeCorrectWithValidData() throws PACDecodingException {
        // A byte array with a length less than 32 should be correct.
        byte[] validData = new byte[31];
        PacCredentialType pacCredentialType = new PacCredentialType(validData);
        assertTrue(pacCredentialType.isCredentialTypeCorrect());
    }

    /**

import static java.util.stream.Collectors.toList;

/**
 * Extracts Kotlin DSL runtime generated sources.
 *
 * Current implementation extracts these from the wrapper's API jars.
 * This is not correct as it should do this with the built distribution instead.
 *
 * Doing it correctly would require running a Gradle build with the full
 * distribution and extracting the generated api jar from its Gradle user home,

	if err != nil {
		return cfg, err
	}

	cfg.Enabled = true
	cfg.DialTimeout = defaultDialTimeout
	cfg.DialKeepAliveTime = defaultDialKeepAlive
	// Disable etcd client SDK logging, etcd client
	// incorrectly starts logging in unexpected data
	// format.
	cfg.LogConfig = &zap.Config{
		Level:    zap.NewAtomicLevelAt(zap.FatalLevel),
		Encoding: "console",
	}
	cfg.Endpoints = etcdEndpoints

            // Act
            SmbNamedPipe pipe = new SmbNamedPipe("smb://server/IPC$/foo", flags, ctx());

            // Assert: observable properties still correct
            assertEquals(flags, pipe.getPipeType());
            assertEquals(SmbConstants.TYPE_NAMED_PIPE, pipe.getType());
        }
    }

    @Test

    @BeforeEach
    void setUp() {
        testCache = new TestBufferCacheImpl(5, 1024); // 5 buffers of 1KB each
    }

    @Test
    @DisplayName("BufferCache interface should define correct method signatures")
    void testInterfaceContract() {
        // Given
        BufferCache cache = mockBufferCache;

        // When & Then - verify interface methods exist and can be called

You will see the automatic API docs for the sub-application, including only its own _path operations_, all under the correct sub-path prefix `/subapi`:

<img src="/img/tutorial/sub-applications/image02.png">

        boostQueryCommand = new BoostQueryCommand();
        boostQueryCommand.register();
    }

    @Test
    public void test_getQueryClassName() {
        // Test that getQueryClassName returns the correct class name
        assertEquals("BoostQuery", boostQueryCommand.getQueryClassName());
    }

    @Test
    public void test_execute_withTermQuery() {
        // Test executing BoostQuery with a TermQuery inside

     * encoded as four 0xFF bytes by {@code writeUTime}.
     */
    @ParameterizedTest(name = "fid={0}, lastWriteTime={1}")
    @MethodSource("validParams")
    @DisplayName("happy: writeParameterWordsWireFormat writes correct bytes")
    void testWriteParameterWordsWireFormat(int fid, long lastWriteTime, byte[] expected) {
        SmbComClose close = new SmbComClose(fid, lastWriteTime);
        byte[] buffer = new byte[10];

## About Starlette { #about-starlette }

You shouldn't pin the version of `starlette`.

Different versions of **FastAPI** will use a specific newer version of Starlette.

So, you can just let **FastAPI** use the correct Starlette version.

## About Pydantic { #about-pydantic }

Pydantic includes the tests for **FastAPI** with its own tests, so new versions of Pydantic (above `1.0.0`) are always compatible with FastAPI.

Vous verrez la documentation API automatique pour la sous‑application, n'incluant que ses propres _chemins d'accès_, tous sous le préfixe de sous‑chemin correct `/subapi` :

<img src="/img/tutorial/sub-applications/image02.png">