assertEquals("correct", f.apply(new Object()));
    assertEquals("correct", f.apply(null));

    Function<@Nullable Object, @Nullable String> g = Functions.constant(null);
    assertEquals(null, g.apply(2));
    assertEquals(null, g.apply(null));

    new EqualsTester()
        .addEqualityGroup(f, Functions.constant("correct"))

            assertEquals(2000000L, basicInfo.getLastWriteTime());
            assertEquals(0L, basicInfo.getSize()); // Basic info always returns 0 for size
        }

        @Test
        @DisplayName("Should generate correct toString for basic info")
        void testBasicInfoToString() {
            Trans2QueryPathInformationResponse.SmbQueryFileBasicInfo basicInfo = response.new SmbQueryFileBasicInfo();

            basicInfo.attributes = 0x20;

        outputBuffer = new byte[1024];
        response = new TransTransactNamedPipeResponse(mockConfig, outputBuffer);
    }

    @Test
    void testConstructor() {
        // Verify that the response is created with correct configuration and buffer
        assertNotNull(response);

        // Use reflection to verify the outputBuffer is set correctly
        try {

    /** The specified user already exists */
    int NT_STATUS_USER_EXISTS = 0xC0000063;
    /** The specified user does not exist */
    int NT_STATUS_NO_SUCH_USER = 0xC0000064;
    /** The specified network password is not correct */
    int NT_STATUS_WRONG_PASSWORD = 0xC000006a;
    /** Logon failure: unknown user name or bad password */
    int NT_STATUS_LOGON_FAILURE = 0xC000006d;
    /** Logon failure: user account restriction */

    // set it as the name of the test.  Then in runTest we can reflectively load and invoke the
    // corresponding method on AbstractFutureTest in the correct classloader.
    TestSuite suite = new TestSuite(AbstractFutureFallbackAtomicHelperTest.class.getName());
    for (Method method : AbstractFutureTest.class.getDeclaredMethods()) {

## Recap { #recap }

You can add multiple body parameters to your *path operation function*, even though a request can only have a single body.

But **FastAPI** will handle it, give you the correct data in your function, and validate and document the correct schema in the *path operation*.

You can also declare singular values to be received as part of the body.

            buildScanTags = listOf("Check"),
            subprojects = JsonBasedGradleSubprojectProvider(File("../.teamcity/subprojects.json")),
        )

    @Test
    fun `create correct PerformanceTest build type for Linux`() {
        val performanceTest =
            PerformanceTest(
                buildModel,
                Stage(
                    StageName.PULL_REQUEST_FEEDBACK,

        MsrpcQueryInformationPolicy policy = new MsrpcQueryInformationPolicy(mockPolicyHandle, level, mockNdrObject);

        // Verify that the super constructor was called with the correct arguments
        // Note: Mockito cannot directly verify super constructor calls.
        // We assume if the object is created, the super constructor was called.
        // We can verify the state of the object after construction.

import static org.junit.jupiter.api.Assertions.assertEquals;

import org.junit.jupiter.api.Test;

/**
 * Tests for the PacConstants interface.
 * This test class verifies that the constant values defined in PacConstants are correct.
 */
class PacConstantsTest {

    /**
     * Tests that the constant values in the PacConstants interface match their expected values.
     * This prevents accidental modification of these critical constants.
     */

If you added the return type annotation, tools and editors would complain with a (correct) error telling you that your function is returning a type (e.g. a dict) that is different from what you declared (e.g. a Pydantic model).