result = response.readParametersWireFormat(smallBuffer, 0, -1);
        assertEquals(0, result);
    }

    @Test
    @DisplayName("Test command type is correct")
    void testCommandType() {
        // Verify that the command is not set in constructor (defaults to 0)
        assertEquals(0, response.getCommand());

        // Verify we can change the subcommand

        // When
        int bytesWritten = response.writeBytesWireFormat(buffer, 0);

        // Then
        assertEquals(0, bytesWritten);
    }

    @Test
    @DisplayName("Should create correct context types")
    void testCreateContext() {
        // Test encryption context
        NegotiateContextResponse enc = Smb2NegotiateResponse.createContext(EncryptionNegotiateContext.NEGO_CTX_ENC_TYPE);

        mimeMap = new MimeMap();
    }

    @Nested
    @DisplayName("getMimeType with extension only")
    class GetMimeTypeWithExtension {

        @Test
        @DisplayName("Should return correct mime type for known extensions")
        void testKnownExtensions() throws IOException {
            assertEquals("application/pdf", mimeMap.getMimeType("pdf"));

  }

  /*
   * This is somewhat of a weak test; we verify that all of the methods are
   * correct, but not that they're actually forwarding correctly. We also rely
   * on the other tests (e.g., SynchronizedSetTest) to verify that the
   * collection views are synchronized correctly.
   */

  public void testSize() {
    int unused = create().size();
  }

  public void testIsEmpty() {

E as ferramentas também ficarão felizes porque `RedirectResponse` e ​​`JSONResponse` são subclasses de `Response`, então a anotação de tipo está correta.

### Anote uma subclasse de Response { #annotate-a-response-subclass }

Você também pode usar uma subclasse de `Response` na anotação de tipo:

{* ../../docs_src/response_model/tutorial003_03_py39.py hl[8:9] *}

/**
 * Extracts Kotlin DSL runtime generated sources.
 *
 * Current implementation extracts these from the wrapper's API jars.
 * This is not correct as it should do this with the built distribution instead.
 *
 * Doing it correctly would require running a Gradle build with the full
 * distribution and extracting the generated api jar from its Gradle user home,
 * slowing down building documentation.
 *

            // Encode at position 100
            int encoded = context.encode(buffer, 100);
            assertEquals(context.size(), encoded);

            // Verify salt is at correct position
            for (int i = 0; i < salt.length; i++) {
                assertEquals((byte) 0xFF, buffer[100 + 4 + 4 + i]);
            }
        }
    }

    @Nested

            populatedArray.s[i] = entry;
        }

        // Replace the info.e field with our populated array
        setDfsEnumArray(dfsRootEnum, populatedArray);

        // Test getEntries returns correct SmbShareInfo objects
        FileEntry[] entries = dfsRootEnum.getEntries();
        assertNotNull(entries);
        assertEquals(3, entries.length);

        // Verify each entry
        for (int i = 0; i < 3; i++) {

        assertTrue(bytesWritten > 0);

        // Verify data is written at correct offset
        assertEquals(3, dst[startOffset]);

        // Verify total parameter count at correct offset
        assertEquals(500, SMBUtil.readInt4(dst, startOffset + 3));

        // Verify total data count at correct offset
        assertEquals(1000, SMBUtil.readInt4(dst, startOffset + 7));
    }

    @Test

                    "Result should be either Unicode or ASCII fallback for " + icon + ", got: " + result);
        }
    }

    @Test
    @DisplayName("should return correct Unicode characters")
    void shouldReturnCorrectUnicodeCharacters() {
        assertEquals('✓', ConsoleIcon.SUCCESS.getUnicodeChar());
        assertEquals('✗', ConsoleIcon.ERROR.getUnicodeChar());