@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

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

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

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

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

### 設定とテスト { #settings-and-testing }

次に、`get_settings` の依存関係オーバーライドを作ることで、テスト中に別の設定オブジェクトを提供するのがとても簡単になります:

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

依存関係オーバーライドでは、新しい `Settings` オブジェクトを作る際に `admin_email` に新しい値を設定し、その新しいオブジェクトを返します。

そして、それが使用されていることをテストできます。

## `.env` ファイルの読み込み { #reading-a-env-file }

{* ../../docs_src/settings/app02_an_py310/main.py hl[17,19:21] *}

### 设置与测试 { #settings-and-testing }

接着，在测试期间，通过为 `get_settings` 创建依赖项覆盖，就可以很容易地提供一个不同的设置对象：

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

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

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

## 读取 `.env` 文件 { #reading-a-env-file }

如果你有许多设置可能经常变化，或在不同环境中不同，那么把它们放进一个文件中，然后像环境变量一样从中读取，可能非常有用。

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

	"github.com/minio/minio/internal/crypto"
	"github.com/minio/minio/internal/hash"
	"github.com/minio/minio/internal/logger"
	"github.com/minio/mux"
	"github.com/minio/pkg/v3/policy"
)

// TestMain to set up global env.
func TestMain(m *testing.M) {
	flag.Parse()

	// set to 'true' when testing is invoked
	globalIsTesting = true

	globalIsCICD = globalIsTesting

	globalActiveCred = auth.Credentials{

pkg syscall (windows-amd64), func FullPath(string) (string, error)

# CL 98150043 testing: add Coverage function, Russ Cox <******@****.***>
pkg testing, func Coverage() float64

# CL 148770043 cmd/go, testing: add TestMain support, Russ Cox <******@****.***>
pkg testing, func MainStart(func(string, string) (bool, error), []InternalTest, []InternalBenchmark, []InternalExample) *M
pkg testing, method (*M) Run() int
pkg testing, type M struct