* broadly guaranteed, but it is observed to be true for OpenJDK 1.7. It also can't be guaranteed
   * that the method isn't inadvertently <i>oversizing</i> the returned set.
   *
   * @param expectedSize the number of elements you expect to add to the returned set
   * @return a new, empty {@code LinkedHashSet} with enough capacity to hold {@code expectedSize}

/// info

The parameter `summary` is available in OpenAPI 3.1.0 and above, supported by FastAPI 0.99.0 and above.

///

## Overriding the defaults { #overriding-the-defaults }

Using the information above, you can use the same utility function to generate the OpenAPI schema and override each part that you need.

But if for some reason your clients depend on the old behavior, you can revert to it by overriding the method `make_not_authenticated_error` in your security classes.

For example, you can create a subclass of `HTTPBearer` that returns a `403 Forbidden` error instead of the default `401 Unauthorized` error:

# Тестування залежностей з переписуваннями { #testing-dependencies-with-overrides }

## Переписування залежностей під час тестування { #overriding-dependencies-during-testing }

Є сценарії, коли ви можете захотіти переписати залежність під час тестування.

Ви не хочете запускати оригінальну залежність (ані будь-які її підзалежності).

# Override Kullanarak Dependency'leri Test Etme { #testing-dependencies-with-overrides }

## Test Sırasında Dependency Override Etme { #overriding-dependencies-during-testing }

Test yazarken bazı durumlarda bir dependency'yi override etmek isteyebilirsiniz.

Orijinal dependency'nin (ve varsa tüm alt dependency'lerinin) çalışmasını istemezsiniz.

import okhttp3.DelegatingSSLSocketFactory
import okhttp3.EventListener
import okhttp3.OkHttpClient
import okhttp3.Request
import org.junit.jupiter.api.Tag
import org.junit.jupiter.api.Test

/**
 * Tests for ALPN overriding on Android.
 */
@Tag("Remote")
class AlpnOverrideTest {
  class CustomSSLSocketFactory(
    delegate: SSLSocketFactory,
  ) : DelegatingSSLSocketFactory(delegate) {

# Probando Dependencias con Overrides { #testing-dependencies-with-overrides }

## Sobrescribir dependencias durante las pruebas { #overriding-dependencies-during-testing }

Hay algunos escenarios donde podrías querer sobrescribir una dependencia durante las pruebas.

No quieres que la dependencia original se ejecute (ni ninguna de las sub-dependencias que pueda tener).

/**
 * {@link FluentFuture} that forwards all calls to a delegate.
 *
 * <p><b>Warning:</b> The methods of {@code ForwardingFluentFuture} forward <b>indiscriminately</b>
 * to the methods of the delegate. For example, overriding {@link #get(long, TimeUnit)} alone
 * <b>will not</b> change the behavior of {@link #get()}, which can lead to unexpected behavior. In
 * this case, you should override {@code get()} as well.
 *

 *
 * <p><b>Warning:</b> The methods of {@code ForwardingListenableFuture} forward
 * <b>indiscriminately</b> to the methods of the delegate. For example, overriding {@link #get(long,
 * TimeUnit)} alone <b>will not</b> change the behavior of {@link #get()}, which can lead to
 * unexpected behavior. In this case, you should override {@code get()} as well.
 *

# Tester des dépendances avec des surcharges { #testing-dependencies-with-overrides }

## Surcharger des dépendances pendant les tests { #overriding-dependencies-during-testing }

Il existe des cas où vous souhaiterez surcharger une dépendance pendant les tests.

Vous ne voulez pas exécuter la dépendance originale (ni ses éventuelles sous‑dépendances).