That's what makes it possible to have multiple automatic interactive documentation interfaces, code generation, etc.

OpenAPI has a way to define multiple security "schemes".

By using them, you can take advantage of all these standard-based tools, including these interactive documentation systems.

OpenAPI defines the following security schemes:

* `apiKey`: an application specific key that can come from:
    * A query parameter.
    * A header.

/**
 * Test class for NtStatus constants
 */
@DisplayName("NtStatus Tests")
class NtStatusTest {

    @Test
    @DisplayName("Should define well-known NT status constants")
    void testWellKnownStatusConstants() {
        // Verify important NT status constants are defined
        assertEquals(0x00000000, NtStatus.NT_STATUS_SUCCESS);
        assertEquals((int) 0xC0000022L, NtStatus.NT_STATUS_ACCESS_DENIED);

# Lifespan Events { #lifespan-events }

You can define logic (code) that should be executed before the application **starts up**. This means that this code will be executed **once**, **before** the application **starts receiving requests**.

The same way, you can define logic (code) that should be executed when the application is **shutting down**. In this case, this code will be executed **once**, **after** having handled possibly **many requests**.

    class InterfaceMethodContractTest {

        @Test
        @DisplayName("Should define exactly four public methods")
        void shouldDefineExactlyFourPublicMethods() {
            java.lang.reflect.Method[] methods = SmbSession.class.getDeclaredMethods();
            assertEquals(4, methods.length, "SmbSession should define exactly 4 methods");
        }

        @Test

 */
@TestInstance(TestInstance.Lifecycle.PER_CLASS)
class FileInformationTest {

    /**
     * Test that interface constants are correctly defined
     */
    @Test
    @DisplayName("Test FileInformation constants are correctly defined")
    void testInterfaceConstants() {
        // Verify all constants have expected values
        assertEquals((byte) 20, FileInformation.FILE_ENDOFFILE_INFO);

    /** End of file reached */
    int NT_STATUS_END_OF_FILE = 0xC0000011;
    /** More processing is required to complete this request */
    int NT_STATUS_MORE_PROCESSING_REQUIRED = 0xC0000016;
    /** Access is denied */
    int NT_STATUS_ACCESS_DENIED = 0xC0000022;
    /** The data area passed to a system call is too small */
    int NT_STATUS_BUFFER_TOO_SMALL = 0xC0000023;
    /** The object name is invalid */

    * Because pydantic data structures are just instances of classes you define; auto-completion, linting, mypy and your intuition should all work properly with your validated data.
* Validate **complex structures**:
    * Use of hierarchical Pydantic models, Python `typing`’s `List` and `Dict`, etc.
    * And validators allow complex data schemas to be clearly and easily defined, checked and documented as JSON Schema.

import static org.junit.jupiter.api.Assertions.assertTrue;

import org.junit.jupiter.api.Test;
import org.mockito.Mockito;

/**
 * Tests for {@link SmbFilenameFilter}. Since the interface only defines
 * a single method, the tests simply ensure that the lambda expression
 * correctly implements the method and that any exception is propagated.
 */
class SmbFilenameFilterTest {

    @Test

     */
    @Test
    @DisplayName("null directory is handled by implementation")
    void handlesNullDirectory() throws Exception {
        SmbFilenameFilter filter = (dir, name) -> dir == null;

        boolean result = filter.accept(null, "anything");

        assertTrue(result, "Filter should accept when dir is null as defined");
    }

    /**

**FastAPI** will know that it can use this dependency to define a "security scheme" in the OpenAPI schema (and the automatic API docs).

/// info | Technical Details