},
		},
		5: {
			desc:       "Correct sha256, nested",
			src:        mustReader(t, bytes.NewReader([]byte("abcd")), 4, "", "", 4),
			size:       4,
			actualSize: 4,
			sha256hex:  "88d4266fd4e6338d13b845fcf289579d209c897823b9217da3e161936f031589",
		},
		{
			desc:       "Correct sha256, nested, truncated",

			pools:          pools,
			name:           "Correct",
			expectedErr:    false,
			expectedUpdate: false,
		},
		{
			meta:           meta,
			pools:          newPools,
			name:           "Correct-Update",
			expectedErr:    false,
			expectedUpdate: true,
		},
		{
			meta:           meta,
			pools:          reducedPools,
			name:           "Correct-Update",
			expectedErr:    false,

    class SamrCloseHandleTests {

        @Test
        @DisplayName("Should construct with correct opnum")
        void testConstructorAndOpnum() {
            // When: Creating close handle message
            samr.SamrCloseHandle message = new samr.SamrCloseHandle(mockPolicyHandle);

            // Then: Should have correct opnum and handle
            assertEquals(0x01, message.getOpnum());

        assertEquals(100, info.sectPerAlloc);
        assertEquals(512, info.bytesPerSect);
        assertEquals(1000L * 100 * 512, info.getCapacity(), "Capacity calculation should be correct");
        assertEquals(500L * 100 * 512, info.getFree(), "Free space calculation should be correct");
    }

    /**
     * Tests the readDataWireFormat method with the SMB_QUERY_FS_SIZE_INFO information level.
     */
    @Test

        assertEquals(2, entries.length, "The number of entries should be correct.");

        // The getEntries method returns FileEntry objects. We can check their names.
        assertEquals("\\domain\share1", entries[0].getName(), "The name of the first share should be correct.");
        assertEquals("\\domain\share2", entries[1].getName(), "The name of the second share should be correct.");
    }

    /**

        // These tests should be removed or replaced with actual constants
    }

    /**
     * Test individual FLAGS2 constants.
     */
    @Test
    @DisplayName("FLAGS2 individual constants are correct")
    void flags2ConstantsTest() {
        // Test individual flag values
        assertEquals(0x0001, SmbConstants.FLAGS2_LONG_FILENAMES);
        assertEquals(0x0002, SmbConstants.FLAGS2_EXTENDED_ATTRIBUTES);

////

## Comillas { #quotes }

//// tab | Prueba

Ayer, mi amigo escribió: "Si escribes 'incorrectly' correctamente, lo habrás escrito incorrectamente". A lo que respondí: "Correcto, pero 'incorrectly' está incorrecto, no '"incorrectly"'".

/// note | Nota

El LLM probablemente traducirá esto mal. Lo interesante es si mantiene la traducción corregida al volver a traducir.

///

////

        @Test
        @DisplayName("Should return correct transport context")
        void testGetTransportContext() throws Exception {
            DcerpcPipeHandle handle = createMockedDcerpcPipeHandle();
            assertEquals(mockContext, handle.getTransportContext());
        }

        @Test
        @DisplayName("Should return correct server name")
        void testGetServer() throws Exception {

Si añadiste la anotación del tipo de retorno, las herramientas y editores se quejarían con un error (correcto) diciéndote que tu función está devolviendo un tipo (por ejemplo, un dict) que es diferente de lo que declaraste (por ejemplo, un modelo de Pydantic).

        @Test
        @DisplayName("Should create correct response type")
        void testCreateResponse() {
            Smb2EchoResponse response = echoRequest.createResponse(mockContext, echoRequest);

            assertNotNull(response);
            assertInstanceOf(Smb2EchoResponse.class, response);
        }

        @Test
        @DisplayName("Should create response with correct configuration")