final Cookie cookie = new Cookie(cookieName, userCode);
        cookie.setMaxAge(age);
        cookie.setHttpOnly(httpOnly);
        if (StringUtil.isNotBlank(cookieDomain)) {
            cookie.setDomain(cookieDomain);
        }
        if (StringUtil.isNotBlank(cookiePath)) {
            cookie.setPath(cookiePath);
        }
        cookie.setSecure(isSecureCookie());

    @Override
    public String getFullUNCPath() {
        return this.fullPath;
    }

    /**
     * {@inheritDoc}
     *
     * @see jcifs.internal.RequestWithPath#getDomain()
     */
    @Override
    public String getDomain() {
        return this.domain;
    }

    /**
     * {@inheritDoc}
     *
     * @see jcifs.internal.RequestWithPath#getServer()
     */
    @Override

### Configuraciones y pruebas

Luego sería muy fácil proporcionar un objeto de configuraciones diferente durante las pruebas al sobrescribir una dependencia para `get_settings`:

{* ../../docs_src/settings/app02/test_main.py hl[9:10,13,21] *}

En la dependencia sobreescrita establecemos un nuevo valor para el `admin_email` al crear el nuevo objeto `Settings`, y luego devolvemos ese nuevo objeto.

Luego podemos probar que se está usando.

{* ../../docs_src/settings/app02/main.py hl[16,18:20] *}

### ⚒ & 🔬

⤴️ ⚫️ 🔜 📶 ⏩ 🚚 🎏 ⚒ 🎚 ⏮️ 🔬 🏗 🔗 🔐 `get_settings`:

{* ../../docs_src/settings/app02/test_main.py hl[9:10,13,21] *}

🔗 🔐 👥 ⚒ 🆕 💲 `admin_email` 🕐❔ 🏗 🆕 `Settings` 🎚, & ⤴️ 👥 📨 👈 🆕 🎚.

⤴️ 👥 💪 💯 👈 ⚫️ ⚙️.

## 👂 `.env` 📁

### Einstellungen und Tests

Dann wäre es sehr einfach, beim Testen ein anderes Einstellungsobjekt bereitzustellen, indem man eine Abhängigkeitsüberschreibung für `get_settings` erstellt:

{* ../../docs_src/settings/app02/test_main.py hl[9:10,13,21] *}

Bei der Abhängigkeitsüberschreibung legen wir einen neuen Wert für `admin_email` fest, wenn wir das neue `Settings`-Objekt erstellen, und geben dann dieses neue Objekt zurück.

        Cookie[] cookies = getMockResponse().getCookies();
        assertTrue(cookies.length > 0);
        assertTrue(cookies[0].getSecure());
        assertEquals("example.com", cookies[0].getDomain());
    }

    public void test_storeSearchParameters_withForwardedProto() {
        getMockRequest().addHeader("X-Forwarded-Proto", "https");
        getMockRequest().setParameter("q", "test");

### Settings and testing { #settings-and-testing }

Then it would be very easy to provide a different settings object during testing by creating a dependency override for `get_settings`:

{* ../../docs_src/settings/app02/test_main.py hl[9:10,13,21] *}

In the dependency override we set a new value for the `admin_email` when creating the new `Settings` object, and then we return that new object.

Then we can test that it is used.

        void testFullUNCPathProperties() {
            testBlock.setFullUNCPath("DOMAIN", "SERVER", "\\\\server\\share\\path");

            assertEquals("DOMAIN", testBlock.getDomain());
            assertEquals("SERVER", testBlock.getServer());
            assertEquals("\\\\server\\share\\path", testBlock.getFullUNCPath());
        }

        @Test
        @DisplayName("Test TID property")

### Configurações e testes

Então seria muito fácil fornecer uma configuração diferente durante a execução dos testes sobrescrevendo a dependência de `get_settings`:

{* ../../docs_src/settings/app02/test_main.py hl[9:10,13,21] *}

Na sobrescrita da dependência, definimos um novo valor para `admin_email` quando instanciamos um novo objeto `Settings`, e então retornamos esse novo objeto.

        this.unicodeHash = unicodeHash;
        hashesExternal = true;
    }

    /**
     * Returns the domain.
     *
     * @return the authentication domain
     */
    public String getDomain() {
        return domain;
    }

    /**
     * Returns the username.
     *
     * @return the username
     */
    public String getUsername() {
        return username;
    }