@DisplayName("Constructor with null pipe name should handle gracefully")
    void testConstructorWithNullPipeName() {
        // Act
        transWaitNamedPipe = new TransWaitNamedPipe(mockConfig, null);

        // Assert
        assertNotNull(transWaitNamedPipe);
        assertNull(transWaitNamedPipe.name);
    }

    @Test
    @DisplayName("Constructor with empty pipe name should handle gracefully")

        context.warning("Test warning message");
        context.detail("Test detail message");
        context.action("Test action message");
    }

    @Test
    @DisplayName("should handle indentation correctly")
    void shouldHandleIndentationCorrectly() {
        UpgradeContext context = TestUtils.createMockContext(Paths.get("/test"));

        // Test indentation methods don't throw exceptions

    /** The specified information class is invalid */
    int NT_STATUS_INVALID_INFO_CLASS = 0xC0000003;
    /** Invalid access to memory location */
    int NT_STATUS_ACCESS_VIOLATION = 0xC0000005;
    /** The handle is invalid */
    int NT_STATUS_INVALID_HANDLE = 0xC0000008;
    /** The parameter is incorrect */
    int NT_STATUS_INVALID_PARAMETER = 0xC000000d;
    /** The system cannot find the device specified */

            assertEquals((byte) 0x00, uuid.node[5]); // Missing data defaults to 0
        }

        @Test
        @DisplayName("Constructor with empty node array in rpc.uuid_t should handle gracefully")
        void testConstructorWithEmptyNode() {
            // Arrange
            rpc.uuid_t rpcUuid = new rpc.uuid_t();
            rpcUuid.time_low = TIME_LOW;
            rpcUuid.time_mid = TIME_MID;

        // Each name should write at least 34 bytes (encoded name + scope)
        assertTrue(bytesWritten >= 68);
    }

    @Test
    @DisplayName("writeTrailerWireFormat with scope should handle scoped names")
    void testWriteTrailerWireFormatWithScope() {
        when(mockCalledName.getName()).thenReturn("SERVER");
        when(mockCalledName.getNameType()).thenReturn(0x20);

     * monitors their progress, and handles cleanup operations.
     *
     * <p>The method:</p>
     * <ul>
     *   <li>Creates crawler threads for each data configuration</li>
     *   <li>Manages concurrent execution based on thread count limits</li>
     *   <li>Monitors thread completion and handles cleanup</li>
     *   <li>Records execution timing and statistics</li>
     * </ul>

handlers = java.util.logging.ConsoleHandler

     */
    boolean generate(String thumbnailId, File outputFile);

    /**
     * Checks if this generator can handle the given document.
     * @param docMap The document map containing metadata.
     * @return True if this generator can handle the document, false otherwise.
     */
    boolean isTarget(Map<String, Object> docMap);

    /**

# Security { #security }

There are many ways to handle security, authentication and authorization.

And it normally is a complex and "difficult" topic.

In many frameworks and systems just handling security and authentication takes a big amount of effort and code (in many cases it can be 50% or more of all the code written).

        NtlmMessage.writeULong(dest, 0, 0x01020304);
        assertArrayEquals(new byte[] { 4, 3, 2, 1 }, dest, "Writer must be little‑endian");
    }

    @Test
    @DisplayName("writeULong handles negative values as unsigned")
    void testWriteULongNegative() {
        byte[] dest = new byte[4];
        NtlmMessage.writeULong(dest, 0, -1);