# 使用覆盖测试依赖项 { #testing-dependencies-with-overrides }

## 测试时覆盖依赖项 { #overriding-dependencies-during-testing }

有些场景下，您可能需要在测试时覆盖依赖项。

即不希望运行原有依赖项（及其子依赖项）。

反之，要在测试期间（或只是为某些特定测试）提供只用于测试的依赖项，并使用此依赖项的值替换原有依赖项的值。

### 用例：外部服务 { #use-cases-external-service }

常见实例是调用外部第三方身份验证应用。

向第三方应用发送令牌，然后返回经验证的用户。

但第三方服务商处理每次请求都可能会收费，并且耗时通常也比调用写死的模拟测试用户更长。

一般只要测试一次外部验证应用就够了，不必每次测试都去调用。

此时，最好覆盖调用外部验证应用的依赖项，使用返回模拟测试用户的自定义依赖项就可以了。

# 用覆寫測試相依 { #testing-dependencies-with-overrides }

## 在測試期間覆寫相依 { #overriding-dependencies-during-testing }

有些情境你可能想在測試時覆寫（override）某個相依（dependency）。

你不希望執行原本的相依（以及它可能具有的任何子相依）。

相反地，你想提供一個只在測試期間使用的不同相依（可能只在特定測試中），並回傳一個可以在原本相依值被使用之處使用的值。

### 使用情境：外部服務 { #use-cases-external-service }

例如你有一個需要呼叫的外部驗證提供者。

你傳送一個 token，它會回傳一個已驗證的使用者。

這個提供者可能按每個請求收費，而且呼叫它可能比在測試中使用固定的模擬使用者多花一些時間。

你大概只想對外部提供者測試一次，而不需要在每個測試都呼叫它。

    inflater.inflate(buffer)
    assertThat(buffer.readUtf8()).isEqualTo("Hello inflation!")
  }

  /**
   * It's possible a self-terminating deflated message will contain trailing data that won't be
   * processed during inflation. If this happens, we need to either reject the message or discard
   * the unreachable data. We choose to discard it!
   *

communication with the community for a specified period. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community

   * testThreshold() which writes exactly enough bytes to fill the buffer, then immediately writes
   * more bytes.
   *
   * <p>Note: Direct testing of the {@link IOException} scenario during write/flush is challenging
   * without mocking. This test verifies that normal operation with threshold crossing still works
   * correctly with the fix in place.
   */

  /** The timestamp of the last taken event, used to measure elapsed time between events. */
  private var lastTimestampNs: Long? = null

  /** Confirm that the thread does not hold a lock on `lock` during the callback. */
  fun forbidLock(lock: Any) {
    forbiddenLocks.add(lock)
  }

  /**
   * Removes recorded events up to (and including) an event is found whose class equals [eventClass]
   * and returns it.

    title: Fine-Grained Authorization for FastAPI
    img: https://fastapi.tiangolo.com/img/sponsors/permit.png
  - url: https://www.interviewpal.com/?utm_source=fastapi&utm_medium=open-source&utm_campaign=dev-hiring
    title: InterviewPal - AI Interview Coach for Engineers and Devs
    img: https://fastapi.tiangolo.com/img/sponsors/interviewpal.png
  - url: https://dribia.com/en/
    title: Dribia - Data Science within your reach

# ADR-0004 - Use a platform-oriented architecture for Gradle

## Status

- ACCEPTED on 2024-02-07

## Context

The Gradle code base is essentially a large monolith, without strong internal boundaries.
This has a number of negative effects on productivity, including:

- Unclear ownership of code.
- Difficult to focus on one particular area.
- Unintended coupling between areas of the code, including tests.

## Decision

        // if some regions were pooled rather than immediately released)
        assertTrue(bufferManager.getTotalReleased() > 0, "Some regions should be released during cleanup");
        assertEquals(allocatedBeforeCleanup, bufferManager.getTotalReleased(),
                "All allocated regions should eventually be released after cleanup");
    }

    @Test

    if [[ "$(git rev-parse --abbrev-ref HEAD)" == "pull_branch" ]]; then
        # TF's CI runs 'git fetch origin "pull/PR#/merge:pull_branch"'
        # To get the as-merged branch during the CI tests
        git diff --diff-filter ACMRT --name-only pull_branch^ pull_branch > $BATS_FILE_TMPDIR/changed_files
    else
        # If the branch is not present, then diff against origin/master