import org.junit.jupiter.params.provider.ValueSource;
import org.mockito.junit.jupiter.MockitoExtension;

/**
 * Tests for StaticJAASConfiguration.
 *
 * Coverage goals:
 * - Happy path with default and custom options.
 * - Null/empty/ignored name parameter handling.
 * - Null options edge case.
 * - Repeated calls equivalence and instance separation.
 * - Interaction check that passed options are not mutated.

              <arg>-Xlint:-removal,-options</arg>
            </compilerArgs>
            <annotationProcessorPaths>
              <path>
                <groupId>com.google.errorprone</groupId>
                <artifactId>error_prone_core</artifactId>
                <version>2.36.0</version>
              </path>
            </annotationProcessorPaths>

              <arg>-Xlint:-removal,-options</arg>
            </compilerArgs>
            <annotationProcessorPaths>
              <path>
                <groupId>com.google.errorprone</groupId>
                <artifactId>error_prone_core</artifactId>
                <version>2.36.0</version>
              </path>
            </annotationProcessorPaths>

                Arguments.of(0x00500001, 0xc0000035), Arguments.of(0x007b0001, 0xc0000033), Arguments.of(0x00320001, 0xC00000BB));
    }

    @ParameterizedTest
    @MethodSource("knownMappings")
    @DisplayName("Happy path: known DOS codes map to expected NTSTATUS")
    void mapsKnownDosCodesToNtStatus(int dosCode, int expectedNtStatus) {
        // Act
        int actual = findNtStatusOrMinusOne(dosCode);

        // Assert

set, and reparse points that are not symlinks, Unix sockets, or dedup files now
always have [`os.ModeIrregular`](/pkg/os#ModeIrregular) set. As a result of these changes,
[`filepath.EvalSymlinks`](/pkg/path/filepath#EvalSymlinks) no longer evaluates
mount points, which was a source of many inconsistencies and bugs.
At previous versions (`winsymlink=0`), mount points are treated as symlinks,

     *
     * @throws CIFSException if an error occurs creating the file
     */
    void createNewFile() throws CIFSException;

    /**
     * Creates a directory with the path specified by this <code>SmbResource</code>
     * and any parent directories that do not exist. This method will fail
     * when used with <code>smb://</code>, <code>smb://workgroup/</code>,

        assertEquals(0L, response.getOffset(), "Offset should be initialized to 0");
    }

    /* ------------------------------------------------------------------ */
    /* 2. Parameter word reading - happy path & edge cases                */
    /* ------------------------------------------------------------------ */

    /**
     * Provides test cases for {@link SmbComSeekResponse#readParameterWordsWireFormat(byte[], int)}.

    * リクエストやレスポンスでは`float`と同じように扱います。

* Pydanticの全ての有効な型はこちらで確認できます: <a href="https://docs.pydantic.dev/latest/concepts/types/" class="external-link" target="_blank">Pydantic data types</a>。
## 例

ここでは、上記の型のいくつかを使用したパラメータを持つ*path operation*の例を示します。

{* ../../docs_src/extra_data_types/tutorial001.py hl[1,2,12:16] *}

関数内のパラメータは自然なデータ型を持っていることに注意してください。そして、以下のように通常の日付操作を行うことができます:

## Simple HTTP Basic Auth

* Importa `HTTPBasic` y `HTTPBasicCredentials`.
* Crea un "esquema de `security`" usando `HTTPBasic`.
* Usa ese `security` con una dependencia en tu *path operation*.
* Devuelve un objeto de tipo `HTTPBasicCredentials`:
  * Contiene el `username` y `password` enviados.

{* ../../docs_src/security/tutorial006_an_py39.py hl[4,8,12] *}

{* ../../docs_src/metadata/tutorial004.py hl[21,26] *}

/// info | Інформація

Детальніше про теги читайте в розділі [Конфігурація шляхів операцій](path-operation-configuration.md#tags){.internal-link target=_blank}.

///

### Перевірка документації

Якщо Ви зараз перевірите документацію, вона покаже всі додаткові метадані: