assertEquals(testServer, shareGetInfo.servername);
    }

    @ParameterizedTest
    @NullAndEmptySource
    @ValueSource(strings = { "", "localhost", "192.168.1.1", "server.domain.com", "\\\\server" })
    void testConstructorWithDifferentServers(String server) {
        // Test with various server values
        MsrpcShareGetInfo shareGetInfo = new MsrpcShareGetInfo(server, testSharename);

ここで、クエリパラメータ `needy` は `str` 型の必須のクエリパラメータです。

以下のURLをブラウザで開くと:

```
http://127.0.0.1:8000/items/foo-item
```

...必須のパラメータ `needy` を加えなかったので、以下の様なエラーが表示されます:

```JSON
{
  "detail": [
    {
      "type": "missing",
      "loc": [
        "query",
        "needy"
      ],
      "msg": "Field required",
      "input": null
    }
  ]
}
```

///

## Валідація даних { #data-validation }

Але якщо ви перейдете у браузері за посиланням [http://127.0.0.1:8000/items/foo](http://127.0.0.1:8000/items/foo), ви побачите гарну HTTP-помилку:

```JSON
{
  "detail": [
    {
      "type": "int_parsing",
      "loc": [
        "path",
        "item_id"
      ],
      "msg": "Input should be a valid integer, unable to parse string as an integer",
      "input": "foo"
    }

        foo.setDuplicateHostName("foo.com");
        duplicateHostHelper.duplicateHostList.add(foo);
        DuplicateHost bar = new DuplicateHost();
        bar.setRegularName("www.bar.com");
        bar.setDuplicateHostName("mail.bar.com");
        duplicateHostHelper.duplicateHostList.add(bar);
        DuplicateHost hoge = new DuplicateHost();
        hoge.setRegularName("www.foo.com");
        hoge.setDuplicateHostName("www.foo.com:99");

  public void testTimeoutOnGetWorksCorrectly() throws InterruptedException, ExecutionException {

    // The task thread waits for the latch, so we expect a timeout here.
    try {
      future.get(20, MILLISECONDS);
      fail("Should have timed out trying to get the value.");
    } catch (TimeoutException expected) {
    } finally {
      latch.countDown();
    }
  }

  /**

    }

    public void setMail_Terms(ConditionOptionCall<TermsAggregationBuilder> opLambda) {
        setMail_Terms("mail", opLambda, null);
    }

    public void setMail_Terms(ConditionOptionCall<TermsAggregationBuilder> opLambda, OperatorCall<BsUserCA> aggsLambda) {
        setMail_Terms("mail", opLambda, aggsLambda);
    }

            // The improved error handling should catch and log any exceptions
            // without propagating them
            controller.delayForWaitingNewUrl();
        } catch (Exception e) {
            fail("delayForWaitingNewUrl should not throw exceptions: " + e.getMessage());
        }
    }

    /**
     * Test boundary values for delay settings
     */
    @Test

pushd "${TFCI_OUTPUT_DIR}"

# Unpack the wheel to get all the file contents. The pure python wheel we built
# above is tagged with "py3-none-any". We cannot change the tags by simply
# renaming the wheels as uploading to PyPI would fail with "File already exists"
# error. In order to upload to PyPI, we unpack the wheel and change the tag
# inside a metadata file to the one we want (e.g cp38-cp38-win_amd) and then

# Hibernate Validator
# -------------------
constraints.CreditCardNumber.message = {item} geçersiz bir kredi kartı numarasıdır.
constraints.EAN.message = {item} geçersiz bir {type} barkodudur.
constraints.Email.message = {item} geçerli bir e-posta adresi değildir.
constraints.Length.message = {item} uzunluğu {min} ile {max} arasında olmalıdır.
constraints.LuhnCheck.message = {value} değerinin Luhn Modulo 11 sağlama toplamı yanlıştır.

    * Числа (`int`, `float`) с минимальными и максимальными значениями и т.п.

* Проверка для более экзотических типов, таких как:
    * URL.
    * Email.
    * UUID.
    * ...и другие.

Все проверки обрабатываются хорошо зарекомендовавшим себя и надёжным **Pydantic**.

### Безопасность и аутентификация { #security-and-authentication }