// Don't call super to avoid actual scheduling in tests
        }

        @Override
        protected void processDirectMemberOf(EntraIdUser user, List<String> groupList, List<String> roleList,
                List<String> groupIdsForParentLookup, String url) {
            processDirectMemberOfCalled.set(true);
            // Don't call super to avoid actual API calls in tests
        }

import org.mockito.junit.jupiter.MockitoExtension;

/**
 * Comprehensive test suite for SmbTransportPool interface.
 * Tests all transport pool operations including connection management,
 * authentication, and lifecycle operations.
 */
@ExtendWith(MockitoExtension.class)
@DisplayName("SmbTransportPool Tests")
class SmbTransportPoolTest {

    @Mock
    private SmbTransportPool transportPool;

    @Mock

import java.util.logging.Level;
import java.util.logging.LogRecord;
import java.util.logging.Logger;
import junit.framework.TestCase;
import org.jspecify.annotations.NullUnmarked;

/**
 * Tests for {@link ServiceManager}.
 *
 * @author Luke Sandberg
 * @author Chris Nokleberg
 */
@NullUnmarked
@GwtIncompatible
@J2ktIncompatible
public class ServiceManagerTest extends TestCase {

如果把它們拆成兩個彼此不共享邏輯或變數的獨立函式，會比較麻煩，你得把值存在全域變數或用其他技巧。

因此，現在建議改用上面介紹的 `lifespan`。

## 技術細節 { #technical-details }

給有興趣鑽研的同好一點技術細節。🤓

在底層的 ASGI 技術規範中，這屬於 [Lifespan Protocol](https://asgi.readthedocs.io/en/latest/specs/lifespan.html) 的一部分，並定義了 `startup` 與 `shutdown` 兩種事件。

/// info

你可以在 [Starlette 的 Lifespan 文件](https://www.starlette.dev/lifespan/) 讀到更多關於 Starlette `lifespan` 處理器的資訊。

也包含如何處理可在程式其他區域使用的 lifespan 狀態。

這部分很正常，多數程式碼你應該已經很熟悉了：

{* ../../docs_src/openapi_callbacks/tutorial001_py310.py hl[7:11,34:51] *}

/// tip

`callback_url` 查詢參數使用的是 Pydantic 的 [Url](https://docs.pydantic.dev/latest/api/networks/) 型別。

///

唯一新的地方是在「路徑操作裝飾器」中加入參數 `callbacks=invoices_callback_router.routes`。我們接下來會看到那是什麼。

## 文件化回呼 { #documenting-the-callback }

實際的回呼程式碼會高度依賴你的 API 應用本身。

而且很可能每個應用都差很多。

   * that gets messy here, and we already have null tests for Range.
   */

  /*
   * These generators also rely on consecutive integer inputs (not necessarily in order, but no
   * holes).
   */

  // SetCreationTester has some tests that pass in duplicates. Dedup them.

func (m *Manager) Targets() []string {
	var res []string
	for k := range m.targets {
		res = append(res, k)
	}
	return res
}

// debugMsg should *only* be used by tests.
//
//lint:ignore U1000 This is used by tests.
func (m *Manager) debugMsg(d debugMsg, args ...any) {
	for _, c := range m.targets {
		c.debugMsg(d, args...)
	}
}

            params.setIsCi(System.getenv("JENKINS_URL") != null);
            params.setDefaultParallel(ParallelDetector.findDefaultParallel(project));
            params.setInFipsJvm(Util.getBooleanProperty("tests.fips.enabled", false));
            params.setIsSnapshotBuild(Util.getBooleanProperty("build.snapshot", true));
            params.setBwcVersions(providers.provider(() -> resolveBwcVersions(rootDir)));
        });

 * @author Louis Wasserman
 */
@GwtCompatible
@Ignore("test runners must not instantiate and run this directly, only via suites we build")
// @Ignore affects the Android test runner, which respects JUnit 4 annotations on JUnit 3 tests.
@SuppressWarnings("JUnit4ClassUsedInJUnit3")
public class MultimapKeysTester<K, V> extends AbstractMultimapTester<K, V, Multimap<K, V>> {
  @CollectionSize.Require(SEVERAL)
  public void testKeys() {

import static org.hamcrest.CoreMatchers.is;
import static org.hamcrest.CoreMatchers.not;
import static org.junit.Assert.assertArrayEquals;
import static org.junit.Assert.assertThat;

import org.junit.Test;

/**
 * Tests for {@link CachedCipher}.
 */
public class CachedCipherTest {

    @Test
    public void testEncryptDecryptBytes() {
        final CachedCipher cipher = new CachedCipher();
        cipher.setKey("mySecretKey");