@Test
    void testWitnessEventTypes() {
        assertEquals(7, WitnessEventType.values().length);

        WitnessEventType[] events = WitnessEventType.values();

        // Verify all expected event types with correct values
        assertEquals(1, WitnessEventType.RESOURCE_CHANGE.getValue());
        assertEquals(2, WitnessEventType.CLIENT_MOVE.getValue());
        assertEquals(3, WitnessEventType.SHARE_MOVE.getValue());

 */
@TestInstance(TestInstance.Lifecycle.PER_CLASS)
class FileInformationTest {

    /**
     * Test that interface constants are correctly defined
     */
    @Test
    @DisplayName("Test FileInformation constants are correctly defined")
    void testInterfaceConstants() {
        // Verify all constants have expected values
        assertEquals((byte) 20, FileInformation.FILE_ENDOFFILE_INFO);

        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

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).

    private Trans2GetDfsReferral trans2GetDfsReferral;

    @BeforeEach
    void setUp() {
        MockitoAnnotations.openMocks(this);
    }

    @Test
    @DisplayName("Constructor should initialize with correct values")
    void testConstructor() throws Exception {
        // Given
        String filename = "\\\\server\\share\\file.txt";

        // When

 * Fix: Change HTTP date formats to UTC to conform to RFC2616 section 3.3.
 * Fix: Support SPDY header blocks with trailing bytes.
 * Fix: Allow `;` as separator for `Cache-Control` header.
 * Fix: Correct bug where HTTPS POST requests were always automatically buffered.
 * Fix: Honor read timeout when parsing SPDY headers.


## Version 1.2.1

_2013-08-23_

    // value. But in the specific case where the bottom two bits of the original number are 01, we
    // want to replace that with 1 in the shifted value for correct rounding.
    return (double) ((value >>> 1) | (value & 1)) * 2.0;
  }

  /** Returns the value of this {@code UnsignedLong} as a {@link BigInteger}. */
  public BigInteger bigIntegerValue() {

        assertTrue(exception.getMessage().contains("DISK_FULL"));
        assertTrue(exception.getMessage().contains("Disk full"));
    }

    @Test
    @DisplayName("Should have correct retryable flags for error codes")
    void testErrorCodeRetryableFlags() {
        // Retryable errors
        assertTrue(SmbOperationException.ErrorCode.CONNECTION_FAILED.isRetryable());

		{
			authString:    "NoV2Prefix",
			expectedError: ErrSignatureVersionNotSupported,
		},
		// Test case - 3.
		// Test case with missing parts in the Auth string.
		// below is the correct format of V2 Authorization header.
		// Authorization = "AWS" + " " + AWSAccessKeyId + ":" + Signature
		{
			authString:    signV2Algorithm,
			expectedError: ErrMissingFields,
		},
		// Test case - 4.

Puedes añadir múltiples parámetros de cuerpo a tu *path operation function*, aunque un request solo puede tener un único cuerpo.

Pero **FastAPI** lo manejará, te dará los datos correctos en tu función, y validará y documentará el esquema correcto en la *path operation*.

También puedes declarar valores singulares para ser recibidos como parte del cuerpo.