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;

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

```Python hl_lines="9-10  13  21"
{!../../docs_src/settings/app02/test_main.py!}
```

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.

        this.challenge = challenge;
        this.ansiHash = ansiHash;
        this.unicodeHash = unicodeHash;
        hashesExternal = true;
    }

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

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

                        .stream().forEach(v -> modifyDeleteEntry(modifyList, attrGivenName, v)));
        final String attrMail = fessConfig.getLdapAttrMail();
        OptionalUtil.ofNullable(user.getMail()).filter(StringUtil::isNotBlank).ifPresent(s -> modifyReplaceEntry(modifyList, attrMail, s))
                .orElse(() -> getAttributeValueList(result, attrMail).stream().forEach(v -> modifyDeleteEntry(modifyList, attrMail, v)));

        setupEpg(_epgMap, et -> ((User) et).getLabeledURI(), (et, vl) -> ((User) et).setLabeledURI(DfTypeUtil.toString(vl)), "labeledURI");
        setupEpg(_epgMap, et -> ((User) et).getMail(), (et, vl) -> ((User) et).setMail(DfTypeUtil.toString(vl)), "mail");
        setupEpg(_epgMap, et -> ((User) et).getMobile(), (et, vl) -> ((User) et).setMobile(DfTypeUtil.toString(vl)), "mobile");

{!> ../../docs_src/settings/app02/main.py!}
```

////

### 设置和测试

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

```Python hl_lines="9-10  13  21"
{!../../docs_src/settings/app02/test_main.py!}
```

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

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

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

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

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

```Python hl_lines="9-10  13  21"
{!../../docs_src/settings/app02/test_main.py!}
```

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.

//// tab | Python 3.9+

```Python hl_lines="12-20"
{!> ../../docs_src/sql_databases/sql_app_py39/alt_main.py!}
```

////

//// tab | Python 3.8+

```Python hl_lines="14-22"
{!> ../../docs_src/sql_databases/sql_app/alt_main.py!}
```

////

/// info

我们将`SessionLocal()`请求的创建和处理放在一个`try`块中。

然后我们在finally块中关闭它。

      assertEquivalent(stats.mean(), streamStats.getAverage());
      assertEquivalent(stats.sum(), streamStats.getSum());
      assertEquivalent(stats.max(), streamStats.getMax());
      assertEquivalent(stats.min(), streamStats.getMin());
    }
  }

  private static void assertEquivalent(double actual, double expected) {
    if (expected == POSITIVE_INFINITY) {
      assertThat(actual).isPositiveInfinity();

          <code>
            <![CDATA[
    /**
     * @see java.lang.Object#toString()
     */
    public String toString()
    {
        return "Contributor {name=" + getName() + ", email=" + getEmail() + "}";
    }
            ]]>
          </code>
        </codeSegment>
      </codeSegments>
    </class>
    <class>
      <name>Dependency</name>
      <version>3.0.0+</version>