// configuration can be null for some plugins
            }
        }
    }

    @Nested
    @DisplayName("Error Handling")
    class ErrorHandlingTests {

        @Test
        @DisplayName("should handle malformed POM gracefully")
        void shouldHandleMalformedPOMGracefully() throws Exception {

        }

        // All threads should complete successfully
        for (boolean s : success) {
            assertTrue(s);
        }
    }

    @DisplayName("Test exception handling for invalid information levels")
    @ParameterizedTest
    @ValueSource(ints = { 0, 1, 2, 4, 5, 6, 8, 100, -2, -100, Integer.MIN_VALUE, Integer.MAX_VALUE })
    void testInvalidInformationLevels(int invalidLevel) {

        assertNotNull(result);
        assertSame(messages, result);
        assertTrue(messages.hasMessageOf(property));
    }

    // Test null property handling
    @Test
    public void test_addErrorsFrontHeader_nullProperty() {
        try {
            messages.addErrorsFrontHeader(null);
            fail("Should throw exception for null property");

            assertTrue((noPropagation & ACE.FLAGS_NO_PROPAGATE) != 0, "Should include no propagate flag");
        }
    }

    @Nested
    @DisplayName("Interface Edge Case Handling")
    class InterfaceEdgeCaseTests {

        @Test
        @DisplayName("Should handle null SID from interface methods")
        void shouldHandleNullSID() {
            ACE ace = mock(ACE.class);

        });
    }

    /**
     * Gets the action response for the specified SSO response type.
     *
     * SPNEGO authentication typically doesn't require special response handling
     * for metadata or logout operations, so this method returns null.
     *
     * @param responseType The type of SSO response requested
     * @return Always returns null for SPNEGO authentication
     */

///

{* ../../docs_src/dependencies/tutorial008b_an_py310.py hl[18:22,31] *}

If you want to catch exceptions and create a custom response based on that, create a [Custom Exception Handler](../handling-errors.md#install-custom-exception-handlers).

## Dependencies with `yield` and `except` { #dependencies-with-yield-and-except }

하지만 필요한 경우 사용할 수 있습니다. 🤓

///

{* ../../docs_src/dependencies/tutorial008b_an_py310.py hl[18:22,31] *}

예외를 잡고 그에 기반해 사용자 정의 응답을 생성하려면, [사용자 정의 예외 처리기](../handling-errors.md#install-custom-exception-handlers)를 생성하세요.

## `yield`와 `except`를 사용하는 의존성 { #dependencies-with-yield-and-except }

        assertNotNull(result);
        assertNotNull(thumbnailJob.sessionId);
        assertTrue(result.contains("Session Id: " + thumbnailJob.sessionId));
        // Exception handling may vary, just verify result is not null
    }

    // Test executeThumbnailGenerator with process failure
    @Test
    public void test_executeThumbnailGenerator_processFailure() {

但是如果你需要，它就在这里。🤓

///

{* ../../docs_src/dependencies/tutorial008b_an_py310.py hl[18:22,31] *}

如果你想捕获异常并基于它创建一个自定义响应，请创建一个[自定义异常处理器](../handling-errors.md#install-custom-exception-handlers)。

## 同时使用 `yield` 和 `except` 的依赖项 { #dependencies-with-yield-and-except }

如果你在带有 `yield` 的依赖中使用 `except` 捕获了一个异常，并且你没有再次抛出它（或抛出一个新异常），FastAPI 将无法察觉发生过异常，就像普通的 Python 代码那样：

但如果你需要，它就在這裡。🤓

///

{* ../../docs_src/dependencies/tutorial008b_an_py310.py hl[18:22,31] *}

如果你想攔截例外並據此回傳自訂回應，請建立一個[自訂例外處理器](../handling-errors.md#install-custom-exception-handlers)。

## 含 `yield` 與 `except` 的相依 { #dependencies-with-yield-and-except }

如果你在含 `yield` 的相依中用 `except` 攔截了例外，且沒有再次拋出它（或拋出新的例外），FastAPI 將無法察覺有例外發生，就像在一般的 Python 中一樣：