assertEquals("FFFE80", Hexdump.toHexString(data2, 0, 6)); // 6 chars = 3 bytes
        assertEquals("FFFE807F", Hexdump.toHexString(data2, 0, 8)); // 8 chars = 4 bytes

        // Test odd size (should handle correctly)
        byte[] data3 = { 0x0A, 0x0B, 0x0C };
        assertEquals("0", Hexdump.toHexString(data3, 0, 1)); // 1 char = 0.5 bytes (rounds up to 1)

            configField.setAccessible(true);
            assertEquals(mockConfig, configField.get(request));
        }

        @Test
        @DisplayName("Should handle null configuration")
        void testConstructorWithNullConfig() {
            assertDoesNotThrow(() -> {
                Smb2EchoRequest request = new Smb2EchoRequest(null);
                assertNotNull(request);

     * @throws SmbException
     */
    synchronized SmbFileHandleImpl ensureOpen() throws CIFSException {
        if (this.handle == null || !this.handle.isValid()) {
            // one extra acquire to keep this open till the stream is released
            if (this.file instanceof SmbNamedPipe) {
                this.handle = this.file.openUnshared(SmbConstants.O_EXCL, ((SmbNamedPipe) this.file).getPipeType() & 0xFF0000, this.sharing,

import org.codelibs.fess.crawler.helper.SitemapsHelper;
import org.codelibs.fess.crawler.processor.ResponseProcessor;

import jakarta.annotation.Resource;

/**
 * A response processor implementation that handles sitemaps.
 * It parses the response body as a SitemapSet, extracts URLs from the sitemaps,
 * and adds them as child URLs to be crawled.
 *
 * <p>
 * This class uses a {@link SitemapsHelper} to parse the sitemap XML or text.

    }

    @Test
    @DisplayName("Constructor with null request should work")
    void testConstructorWithNullRequest() {
        // Test that null request is handled properly
        SmbNegotiation negotiationWithNullRequest = new SmbNegotiation(null, mockResponse, testRequestBuffer, testResponseBuffer);

        assertNull(negotiationWithNullRequest.getRequest());

Routes are declared in a single place, using functions declared in other places (instead of using decorators that can be placed right on top of the function that handles the endpoint). This is closer to how Django does it than to how Flask (and Starlette) does it. It separates in the code things that are relatively tightly coupled.

/// check | Inspired **FastAPI** to

            // Should use caller available units, not actual free units
            assertEquals(500L * 8 * 512, fileFsFullSizeInfo.getFree());
        }

        @Test
        @DisplayName("Should handle negative values in buffer")
        void shouldHandleNegativeValuesInBuffer() throws SMBProtocolDecodingException {
            // Given - negative values (treated as unsigned in protocol)

        assertEquals(4, attemptCount.get());
    }

    /**
     * Test: Null safety in connect() when targetIndices is null
     * Verifies that connect() handles null targetIndices gracefully
     */
    @Test
    public void testConnectWithNullTargetIndices() {
        final AdminClient mockAdminClient = mock(AdminClient.class);

            assertEquals(2048, response.getEndOfFile());
            assertEquals(0x10, response.getFileAttributes());
        }

        @Test
        @DisplayName("Should handle all zero values correctly")
        void testReadBytesWireFormatWithZeroValues() throws SMBProtocolDecodingException {
            // Given
            byte[] buffer = new byte[60];

        @Test
        @DisplayName("Should handle null buffer in decode")
        void testNullBuffer() {
            FileFsSizeInformation info = new FileFsSizeInformation();

            assertThrows(NullPointerException.class, () -> {
                info.decode(null, 0, 0);
            });
        }

        @Test
        @DisplayName("Should handle insufficient buffer length")