String result = data.toString();
        assertNotNull(result);
        assertTrue(result.contains("ExtractData"));
    }

    public void test_complexScenario() {
        // Test complex scenario with multiple operations
        ExtractData data = new ExtractData();

        // Set content

    void testCapacityEdgeValues(long capacity) {
        when(mockAllocInfo.getCapacity()).thenReturn(capacity);
        assertEquals(capacity, mockAllocInfo.getCapacity());
    }

    /**
     * Null pointer scenario – calls on a null reference should raise
     * {@link NullPointerException}. This test is defensive; in real code it
     * would likely be handled elsewhere.
     */
    @Test

    @Test
    @DisplayName("send with explicit null varargs propagates exception from implementation")
    void send_nullVarargsArray_throws() throws Exception {
        // Arrange: passing explicit null vararg array is edge scenario
        when(tree.send(eq(request), isNull())).thenThrow(new CIFSException("null params"));

        // Act + Assert

 * provides {@code static final} constants, so the test suite focuses on
 * value correctness, bit‑mask logic, and some derived properties.
 *
 * <p>Mockito is exercised in a dummy scenario to satisfy the
 * request for an interaction test.  The mock represents a
 * {@code SmbTransport} collaborator and is used only for
 * demonstration – the real class behaviour is not required for
 * validating constants.
 */

        // data1 should also be modified (same object)
        assertEquals("https://modified.com", data1.getUrl());
    }

    public void test_complexScenarioWithGet() {
        // Test complex scenario with GET method
        RequestData data = RequestDataBuilder.newRequestData().get().url("https://api.example.com/users/123").weight(0.8f).build();

        assertEquals(Method.GET, data.getMethod());

        SmbRenewableCredentials impl = supplier.get();

        // Act: call renew
        CredentialsInternal renewed = impl.renew();

        // Assert: verify behavior based on scenario
        if (expectSame) {
            assertSame(impl, renewed, "renew() should return the same instance");
        } else if (expectNew) {
            assertNotNull(renewed, "renew() should return a new non-null instance");

        // Test close without any file
        ResponseData data = new ResponseData();
        data.close(); // Should not throw exception
    }

    public void test_complexScenario() {
        // Test complex scenario with multiple operations
        ResponseData data = new ResponseData();

        // Set various properties
        data.setUrl("https://example.com/page");
        data.setHttpStatusCode(200);

5. **Resources**: Test resources are properly managed and cleaned up

## Contributing

When adding new tests:
1. Follow the existing naming convention: `test_<method>_<scenario>_<expectedResult>`
2. Add clear JavaDoc comments explaining the test purpose
3. Ensure tests are independent and can run in any order
4. Clean up resources in finally blocks or use try-with-resources

            assertEquals(500L * sectorSize, fileFsFullSizeInfo.getFree());
        }

        @Test
        @DisplayName("Should handle full disk scenario")
        void shouldHandleFullDiskScenario() throws SMBProtocolDecodingException {
            // Given - disk with no free space
            ByteBuffer buffer = ByteBuffer.allocate(32);

      required: false

  - type: markdown
    attributes:
      value: >
        #### Ubiquity: provide concrete use cases


        Did you *actually* encounter the need for this feature in a real-world scenario, or is it
        just a feature that seems like a sensible addition to Guava?


        Before new features get added to Guava, we really want to be sure that it's for a use case