assertEquals("container", exception.getComponentName());
    }

    @Test
    public void test_getComponentName() {
        // Test getComponentName method with various scenarios
        String componentName1 = "dataSource";
        ContainerNotAvailableException exception1 = new ContainerNotAvailableException(componentName1, new RuntimeException());

        assertTrue(memory2 >= 0);
        // Memory usage should have changed (though we can't guarantee direction due to GC)
    }

    @Test
    public void test_integrationScenarios() {
        // Test realistic scenarios combining multiple methods
        String memoryLog1 = MemoryUtil.getMemoryUsageLog();

        // Create some objects and measure their sizes
        List<String> testData = new ArrayList<>();

## 1. Overview

Persistent handles (also known as durable handles) allow SMB3 connections to survive network disconnections, server reboots, and client reconnections. This feature is critical for enterprise reliability and seamless failover scenarios.

## 2. Protocol Specification Reference

- **MS-SMB2 Section 2.2.13.2.3**: SMB2_CREATE_DURABLE_HANDLE_REQUEST
- **MS-SMB2 Section 2.2.13.2.4**: SMB2_CREATE_DURABLE_HANDLE_REQUEST_V2

_2014-03-17_

 * Fix bug where deleting a file that was absent from the `HttpResponseCache`
   caused an IOException.
 * Fix bug in HTTP/2 where our HPACK decoder wasn't emitting entries in
   certain eviction scenarios, leading to dropped response headers.

## Version 1.5.1

_2014-03-11_

 * Fix 1.5.0 regression where connections should not have been recycled.

import org.dbflute.optional.OptionalThing;
import org.junit.jupiter.api.Test;

/**
 * Edge case tests for RankFusionProcessor.
 * Tests boundary conditions, empty states, and error scenarios.
 */
public class RankFusionProcessorEdgeCaseTest extends UnitFessTestCase {

    private static final String ID_FIELD = "_id";

    /**
     * Test behavior when no searchers are registered (empty list).
     */

            verify(mockSession, times(1)).unwrap(SmbSession.class);
            verify(mockSession, times(1)).close();
        }

        @Test
        @DisplayName("Should support partial mocking scenarios")
        void shouldSupportPartialMockingScenarios() {
            SmbSession mockSession = mock(SmbSession.class);
            Configuration mockConfig = mock(Configuration.class);

Sie werden es wahrscheinlich nicht direkt in Ihrem Code verwenden müssen.

Aber falls Sie es für ein fortgeschrittenes Szenario benötigen, können Sie benutzerdefinierte Header hinzufügen:

{* ../../docs_src/handling_errors/tutorial002_py310.py hl[14] *}

## Benutzerdefinierte Exceptionhandler installieren { #install-custom-exception-handlers }

        };
        ComponentUtil.setFessConfig(fessConfig);

        ssoManager = new SsoManager();
        assertEquals(expectedSsoType, ssoManager.getSsoType());
    }

    // Test full integration scenarios
    @Test
    public void test_fullScenario_ssoEnabled() {
        currentSsoType = "saml";
        final LoginCredential expectedCredential = new TestLoginCredential("samluser");

        assertTrue(actual.contains("10.0.0.5"), "toString should contain the second NbtAddress string representation");
    }

    /**
     * Helper method to set common superclass fields for successful parsing scenarios.
     */
    private void setSuperclassFieldsForSuccessfulParsing() throws NoSuchFieldException, IllegalAccessException {
        Field resultCodeField = NameServicePacket.class.getDeclaredField("resultCode");

Probablemente no necesitarás usarlos directamente en tu código.

Pero en caso de que los necesites para un escenario avanzado, puedes agregar headers personalizados:

{* ../../docs_src/handling_errors/tutorial002_py310.py hl[14] *}

## Instalar manejadores de excepciones personalizados { #install-custom-exception-handlers }