# 依存関係のオーバーライドによるテスト { #testing-dependencies-with-overrides }

## テスト時の依存関係のオーバーライド { #overriding-dependencies-during-testing }

テスト中に依存関係をオーバーライドしたい場面がいくつかあります。

元の依存関係（およびそれにぶら下がるサブ依存関係）を実行したくない場合です。

代わりに、テストの間だけ（特定のテストだけでも）使われる別の依存関係を提供し、元の依存関係の値が使われていた箇所で利用できる値を返したいのです。

### ユースケース: 外部サービス { #use-cases-external-service }

例として、呼び出す必要がある外部の認証プロバイダがあるとします。

トークンを送ると、認証済みユーザーが返ってきます。

   * resizing the table, as well as populating slots with new Cells.
   * There is no need for a blocking lock; when the lock is not
   * available, threads try other slots (or the base).  During these
   * retries, there is increased contention and reduced locality,
   * which is still better than alternatives.
   *
   * Per-thread hash codes are initialized to random values.

 * and validate remote repositories for artifact resolution, dependency collection,
 * model building, and other Maven operations.
 *
 * <p>Implementations of this interface can specify a list of remote repositories
 * to be used during the operation. If no repositories are specified (null),
 * the session's default remote repositories will be used. The repositories
 * are validated to ensure they don't contain duplicates or null entries.
 *

```
...
        "MetaUsr": {
         "X-Amz-Restore-Expiry-Days": "4",
          "X-Amz-Restore-Request-Date": "Mon, 22 Feb 2021 21:10:09 GMT",

after replication attempt either succeeded or failed respectively. On the destination side, a `X-Amz-Replication-Status` status of `REPLICA` indicates that the object was replicated successfully. Any replication failures are automatically re-attempted during a periodic disk scanner cycle.

To perform bi-directional replication, repeat the above process on the target site - this time setting the source bucket as the replication target. It is recommended that replication be run in a system with...

* **Modify some DNS records**.
    * For this, the renewal program needs to support the APIs of the DNS provider, so, depending on the DNS provider you are using, this might or might not be an option.
* **Run as a server** (at least during the certificate acquisition process) on the public IP address associated with the domain.
    * As we said above, only one process can be listening on a specific IP and port.

)

if NOT "%FESS_HEAP_SIZE%" == "" (
set FESS_MIN_MEM=%FESS_HEAP_SIZE%
set FESS_MAX_MEM=%FESS_HEAP_SIZE%
)

REM min and max heap sizes should be set to the same value to avoid
REM stop-the-world GC pauses during resize, and so that we can lock the
REM heap in memory on startup to prevent any of it from being swapped
REM out.
set FESS_JAVA_OPTS=%FESS_JAVA_OPTS% -Xms%FESS_MIN_MEM% -Xmx%FESS_MAX_MEM%

        // Release the session (back to initial state)
        session.release();
        assertFalse(session.isInUse(), "Session should not be in use after release");
    }

    /**
     * Test exception handling during cleanup
     */
    @Test
    @Timeout(5)
    public void testExceptionHandling() throws Exception {
        SmbSessionImpl session = new SmbSessionImpl(mockContext, "testhost", "testdomain", mockTransport);

        // Test with source offset + length exceeding source array bounds
        byte[] data = { 0x01, 0x02 };
        // This constructor call itself should not throw an error, as it's just storing the values.
        // The error should occur when System.arraycopy is called.
        ByteEncodable encodable = new ByteEncodable(data, 1, 2); // off=1, len=2, data.length=2. 1+2 > 2

        byte[] dest = new byte[5];

- All versioned buckets maintain the same order for "versions" for each object after being decommissioned to the other pools.
- A pool interrupted during the decommission process, such as for a cluster restart, resumes from where it left off.

## How to decommission a pool

```
λ mc admin decommission start alias/ http://minio{1...2}/data{1...4}
```