import org.jspecify.annotations.Nullable;

/**
 * A {@link BlockingQueue} which forwards all its method calls to another {@link BlockingQueue}.
 * Subclasses should override one or more methods to modify the behavior of the backing collection
 * as desired per the <a href="http://en.wikipedia.org/wiki/Decorator_pattern">decorator
 * pattern</a>.
 *

   *
   * <p><b>Warning: do not depend</b> on the behavior of this method.
   *
   * <p>Historically, {@code Equivalence} instances in this library have implemented this method to
   * recognize certain cases where distinct {@code Equivalence} instances would in fact behave
   * identically. However, as code migrates to {@code java.util.function}, that behavior will
   * disappear. It is best not to depend on it.
   */
  @Override

    }

    /**
     * Parameterized version of testActivatedDefaultProfileBySource that demonstrates
     * cross-platform path behavior using JIMFS to simulate both Windows and Unix file systems.
     * This test shows how the path separator expectations differ between platforms.
     */
    @ParameterizedTest(name = "testActivatedDefaultProfileBySource[{0}]")

            }
        }
        assertThrows(ClassCastException.class, () -> {
            OtherPipeHandle result = target.unwrap(OtherPipeHandle.class);
        });

        // Null input: document current behavior (NPE from isAssignableFrom)
        assertThrows(NullPointerException.class, () -> target.unwrap(null));
    }

    @Test
    @DisplayName("getPipe, getPipeType, getUncPath delegate to underlying pipe")

   * value that are {@linkplain Range#isConnected connected} to this range.
   *
   * <p>The behavior of {@link #get(Comparable) get(k)} after calling this method is identical to
   * the behavior described in {@link #put(Range, Object) put(range, value)}, however the ranges
   * returned from {@link #asMapOfRanges} will be different if there were existing entries which

import java.io.ObjectOutputStream;

import org.junit.jupiter.api.DisplayName;
import org.junit.jupiter.api.Test;

import jcifs.BaseTest;
import jcifs.CIFSException;

/**
 * Tests for SpnegoException constructors and behavior.
 */
@DisplayName("SpnegoException Tests")
class SpnegoExceptionTest extends BaseTest {

    @Test
    @DisplayName("Should create SpnegoException with default constructor")
    void testDefaultConstructor() {

class SmbComCreateDirectoryTest {

    private Configuration mockConfig;

    @BeforeEach
    void setUp() {
        // Mock the Configuration object
        mockConfig = mock(Configuration.class);
        // Define behavior for the OEM encoding, which is used by writeString
        when(mockConfig.getOemEncoding()).thenReturn(StandardCharsets.UTF_8.name());
    }

    @Test
    void testConstructor() {

import org.junit.jupiter.api.DisplayName;
import org.junit.jupiter.api.Test;
import org.mockito.Mock;

/**
 * Comprehensive test suite for Address interface.
 * Tests the contract and behavior of Address implementations.
 */
@DisplayName("Address Interface Tests")
class AddressTest extends BaseTest {

    @Mock
    private CIFSContext mockContext;

    @Mock
    private Address mockAddress;

 *    thread's [uncaught exception handler][Thread.UncaughtExceptionHandler]. By default this
 *    crashes the application on Android and prints a stacktrace on the JVM. (Crash reporting
 *    libraries may customize this behavior.)
 *
 * A good way to signal a failure is with a synthetic HTTP response:
 *
 * ```kotlin
 *   @Throws(IOException::class)
 *   override fun intercept(chain: Interceptor.Chain): Response {

 *       String}.
 *   <li>{@code getElement} on a {@code Multiset.Entry<@Nullable String>} returns {@code @Nullable
 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},