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_an_py39/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.

        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")

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_an_py39/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.

Então seria muito fácil fornecer um objeto de configurações diferente durante os testes criando uma sobrescrita de dependência para `get_settings`:

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

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

Depois podemos testar que ele é usado.

            }
            throw new SmbException(resp.getErrorCode(), null);
        }

        if (req.getDomain() != null && getContext().getConfig().isDfsConvertToFQDN() && dr instanceof DfsReferralDataImpl) {
            ((DfsReferralDataImpl) dr).fixupDomain(req.getDomain());
        }
        if (log.isDebugEnabled()) {
            log.debug("Got referral " + dr);
        }

        return convertEmptyToNull(labeledURI);
    }

    public void setLabeledURI(String value) {
        registerModifiedProperty("labeledURI");
        this.labeledURI = value;
    }

    public String getMail() {
        checkSpecifiedProperty("mail");
        return convertEmptyToNull(mail);
    }

    public void setMail(String value) {
        registerModifiedProperty("mail");
        this.mail = value;

    @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

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_an_py39/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_an_py39/main.py hl[17,19:21] *}

### 设置和测试

然后，在测试期间，通过创建 `get_settings` 的依赖项覆盖，很容易提供一个不同的设置对象：

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

在依赖项覆盖中，我们在创建新的 `Settings` 对象时为 `admin_email` 设置了一个新值，然后返回该新对象。

然后，我们可以测试它是否被使用。

## 从 `.env` 文件中读取设置

如果您有许多可能经常更改的设置，可能在不同的环境中，将它们放在一个文件中，然后从该文件中读取它们，就像它们是环境变量一样，可能非常有用。

        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;
    }