QueryBuilders.matchAllQuery(), 10, (hit, accumulator) -> accumulator.add(hit.getSourceAsMap()));

        assertNotNull(results);
        assertEquals(3, results.size());

        // Verify we can access the source data
        for (Map<String, Object> result : results) {
            assertTrue(result.containsKey("name"));
            assertTrue(result.containsKey("value"));
        }
    }

   *       should throw {@link IllegalArgumentException}.
   *   <li>{@link CharEscaper} handles Java characters independently and does not verify the input
   *       for well formed characters. A {@code CharEscaper} should not be used in situations where
   *       input is not guaranteed to be restricted to the Basic Multilingual Plane (BMP).
   * </ul>
   *

    suite.addTestSuite(ImmutableTypeToInstanceMapTest.class);

    suite.addTest(
        MapTestSuiteBuilder.using(
                new TestTypeToInstanceMapGenerator() {
                  // Other tests will verify what real, warning-free usage looks like
                  // but here we have to do some serious fudging
                  @Override
                  @SuppressWarnings({"unchecked", "rawtypes"})

        // Assert
        assertNotNull(result);
        assertTrue(result.contains("pipeName=" + specialPipeName));
    }

    @Test
    @DisplayName("Verify parent class command types")
    void testParentClassCommandTypes() {
        // Arrange
        transWaitNamedPipe = new TransWaitNamedPipe(mockConfig, testPipeName);

        // Assert

        m.call_id = 0x123;

        NdrBuffer buf = new NdrBuffer(new byte[1024], 0);
        m.encode(buf);

        // Reset to read what was written
        buf.setIndex(0);

        // Verify header was written correctly
        assertEquals(5, buf.dec_ndr_small()); // RPC version
        assertEquals(0, buf.dec_ndr_small()); // minor version
        assertEquals(0, buf.dec_ndr_small()); // ptype

		}
	}
	config.Lock()
	delete(config.Tiers, tier)
	delete(config.drivercache, tier)
	config.Unlock()
	return nil
}

// Verify verifies if tier's config is valid by performing all supported
// operations on the corresponding warmbackend.
func (config *TierConfigMgr) Verify(ctx context.Context, tier string) error {
	d, err := config.getDriver(ctx, tier)
	if err != nil {
		return err
	}

  static Thread startThread(Runnable runnable) {
    Thread thread = new Thread(runnable);
    thread.setDaemon(true);
    thread.start();
    return thread;
  }

  /**
   * Generates a test case verifying that calling any enterXxx, tryEnterXxx, or waitForXxx method
   * with a guard that doesn't match the monitor produces an IllegalMonitorStateException.
   */
  private static TestCase generateGuardWithWrongMonitorTestCase(

在这个异常中，我们包含所需的作用域（如果有的话），以空格分隔的字符串（使用 `scope_str`）。我们把这个包含作用域的字符串放在 `WWW-Authenticate` 响应头中（这是规范要求的一部分）。

{* ../../docs_src/security/tutorial005_an_py310.py hl[106,108:116] *}

## 校验 `username` 与数据形状 { #verify-the-username-and-data-shape }

我们校验是否获取到了 `username`，并提取作用域。

然后使用 Pydantic 模型验证这些数据（捕获 `ValidationError` 异常），如果读取 JWT 令牌或用 Pydantic 验证数据时出错，就抛出我们之前创建的 `HTTPException`。

在這個例外中，我們把所需的 scopes（若有）以空白分隔的字串形式（透過 `scope_str`）加入，並將該包含 scopes 的字串放在 `WWW-Authenticate` 標頭中（這是規格的一部分）。

{* ../../docs_src/security/tutorial005_an_py310.py hl[106,108:116] *}

## 驗證 `username` 與資料結構 { #verify-the-username-and-data-shape }

我們先確認取得了 `username`，並取出 scopes。

接著用 Pydantic 模型驗證這些資料（捕捉 `ValidationError` 例外），若在讀取 JWT token 或用 Pydantic 驗證資料時出錯，就丟出先前建立的 `HTTPException`。

        processMethod.setAccessible(true);

        try {
            Integer result = (Integer) processMethod.invoke(null, options);
            assertNotNull(result);
            // Verify that generate was called at least once
            assertTrue(generateCallCount.get() >= 0);
        } catch (Exception e) {
            // Expected behavior when components are not fully initialized